Hi All,

Is there a way to control the field validation message??

I would like to be able to have both French & English messages

based on a global (selected language) field.

I could always type short bilingual message in the box

but I am hoping for a better way!!??

Thanks

--Dan

The only method I can think of would involve turning off the field-level validation and creating pseudo-validation using the Custom Dialog Box script step. This will entail having complete control over the user interface however.

The process would be something like this: user enters a data entry screen, enters or edits field values; to complete the data entry they run a script that checks the field entries and displays the appropriate message.

I think I would go bi-lingual using the standard mechanism... unless you foresee the need for more languages.

You need to be a bit careful because error / message windows on the Mac (I'm not sure about Windows) do NOT grow, so if you've got too much text it simply gets chopped off.

On Windows, you can make the message windows bigger, but they do not appear to stay that way across multiple machines, only the local one.

Thank you all for the speedy replies!!

Any ideas why FM (5.5v2) has a bunch of error # (500 - 507) that

mention various failed "validation entry option".

How / when would they get triggered & trapped with script??

Thanks

--Dan

Copied from FM help:

Error Codes

500 Date value does not meet validation entry options

501 Time value does not meet validation entry options

502 Number value does not meet validation entry options

503 Value in field is not within the range specified in validation entry options

504 Value in field is not unique as required in validation entry options

505 Value in field is not an existing value in the database as required in validation entry options

506 Value in field is not listed on the value list specified in validation entry option

507 Value in field failed calculation test of validation entry option

On Windows, you can make the message windows bigger, but they do not appear to stay that way across multiple machines, only the local one

I think this is because dialog sizes would be stored in the program memory. So the sizes are specific to the FileMaker program.

I remember before 5.5 it wouldn't even keep the dialog size!

Ken