To make field validation for globals possible I found a trick. I change the field back to a number field, or text field (whatever kind of field the global was), and then I set the field validation. Then I change the field type back to global.

It will be a known trick I think, but worth to remember. My only question is, is it safeproof, in other words, can this have any negative effects?

And frankly I don't understand why FM has blocked out the direct setting of field validation for globals.

Harryk

Hi

I didn't validate by calculation, but I tried to validate a not empty on a field, then change it back to a global and it didn't work.

However I do agree that it is unfortunate that FM has locked out these features. Another thing I don't like is related to number and date fields. For some reason you can't justify these types of fields. You have to change them to text fields, justify them, then change them back. It's stupid (unless I am stupid because I am missing something).

Ken

mmm, as validation by calculation seems to work with me with globals you could try the IsEmpty(field) in a calculation with that global.

Harryk

I've had call to use not IsEmpty("gGlobalField" as a validation on a global field on a number of occasions, and can confirm that it works (as do the strict and custom message options).

I don't believe it is a matter of FM 'locking out' validation features for globals as such - rather, it is simply the case that they didn't ever bother to add them in.

In the same way that globals should be able to be accessed when placed in the header or footer in list view, but aren't... It is a case of the implementation of globals being another job half-done.

I think the principle they've been working to for a number of years is that you get a new feature to the point where there is just enough there for the marketing department to be able to advertise it and then drop it and move on to something else.

It is a crying shame, because FM is a great program which could be even greater.

Actually, the technique of defining a field as a non-global, setting its validation and then changing it to a global has worked through many revisions of Filemaker, so it's very close to being the official way of doing it. Of course, just wait until the next version comes out and it won't work anymore.

Too right, Bob.

Well, so long as they provide another means to set up validations for globals - official or otherwise - I guess we'll all adapt as usual