Validation "on record level"

[stevie.at]

Besides all the previous postings, tech articles and hints I struggle with a validation in FMP7...

I want users to make "clean" entries by defining some "must" fields. Actually there are several portals in my solution and 2 of them should contain at least 1 record. As all of the dedicated fields (including the one that counts the portal entries) are calculation fields another field has to do the job.

What I read was that a calculation should do it best, but so far it didn't work out. I tried almost every combination of the settings...at no point a validation on record level worked.

Ideally I think of a calculation if my fields that count the portal rows are empty the user gets the error message and can't exit the record.

[Vaughan]

As far as I know there is no way for a "calculation" to automatically create related records.

However, it is very easy to script the process... the hard part is making sure the users use the scripts to create new records. This is then becomes an interface issue: you'll need to disable the menus using passwords and create buttons and scripts to perform or invoke all the required functions that are required.

It's not suck a hard job, in fact most pro designed solutions tend to implement this sort of interface conrol all the time. It's the only way to get rid of the dreaded "Delete All record" command!

[aaa]

You want to get anythink like this?

See attachment.

Example.zip

[stevie.at]

Thanks for posting, guys!

Vaughan:

It's not about creating and deleting records. Users do use my scripted buttons. All I need is a simple way to make sure certain portals contain data what should work with validation. But instead of validation after editing a certain field it should just work whenever a user wants to exit the record - like one validation for the whole record.

aaa:

Well, this simple way might look impressive for a user and is of course easy to implement but doesn't prevent anyone from exiting the record without doing the minimum required entries. The problem is that calculated fields cannot be validated so I need an additional field to do so...problem's how...

[Vaughan]

Put validation on the fields in the related tables. They will validate through a portal too.

[stevie.at]

The fields I use in the portal are either calculated fields or actually do some other validation yet.

And again the problem is if I use any other fields the valiation works when this field is modified or always, whatever option you check if you do it with a calculation.

Anyway, it's always on field level, never on record level. Whatever other way of validation I tried the result was all the same.

...seems like there is no way to validate just when commit (exit) a specific record?