Validation Problem

[Bob White]

In a runtime solution that I am creating, there are several fields (some text and some numeric only) that I have turned on the "maximum number of characters" feature under the validation tab within Define Fields. These work as they should in FMP. However, after the runtime is created with FM Developer, these particular validations don't work. (In other words, I can type as many characters as I want in said fields, in the runtime version, and just tab to any other field and not get the expected error message about the field being defined for a maximum of x characters.) All other validations that I have set work just fine.

I am using FMP 5.5 v2 for development and FM Developer Tool 5.0 v1. Would appreciate any advice on resolving this probem. Thanx, Bob.

[The Bridge]

I imagine that the problem lies in using Developer v.5 to bind FMP 5.5 files -- any v5.5 features will likely be ignored by the developer version. You will likely have to upgrade to Developer 6 to take advantage of that particular validation and other 5.5+ features.

The good news is that there's a rebate available for Developer 5 users who upgrade to 6!

[SteveB]

There is a version upgrade of Developer that FM released about 2 weeks ago which you should download and install.

[Bob White]

Thank you both for the advice. However, working a large government agency, I can't just run out and buy the new version to solve problems. Just not an option. Also, the last updater for Developer 5.0 that I can find at the updaters page is from June, 2001, and was a driver update. Also, the feature which is not working isn't anything new --- max character validation has been around since probably FMP3 if not earlier.

Would it be possible for one you that is using 5.5 on both products to do a tiny test? Like create a single field db, define the field for a max character limit and make the db into a runtime and see if the validation works. That, hopefully, would tell us whether or not I have a version problem. Thanx in advance.

[The Bridge]

I stand by my statement. Max Character appeared first in FileMaker 5.5. At your request, I created a one-field database in 5.5 with Max Character validation on the field. I bound the file in FileMaker 5.5 Developer; validation worked. I bound the file again in FileMaker 5 Developer, validation did not work. But when opened in FileMaker 5.5, the bound file validation worked.

In order to take advantage of FileMaker 5.5's features in a runtime, including Max Character validation, you must bind the file in FileMaker 5.5 Developer edition.

[CobaltSky]

Yes, I'm afraid Peter is correct, the specific validation option "Maximum number of characters" first appeared in FMPv5.5 and isn't supported by v5 or earlier - either desktop or runtime versions.

Quite apart from the fact that it simply doesn't appear in the validation options dialog for v5, v4 or v3, I note that it is also listed as a new feature in the article on the FMI kbase called "Database Design Changes In FileMaker Pro 5.5" at http://www.filemaker.com/ti/107470.html

However a solution to your problem lies in using the 'Validation by calculation' option which is available in v5, and also works in v5 runtimes. Eg to implement a maximum of 17 characters by this method (for a field called 'YourField'), you'd specify the calculation validation formula as: Length(YourField) < 18.

This approach is v5 runtime compatible, but will work just as well in the standard/desktop editions of v5 as well as v5.5 or v6.

[Bob White]

My apologies and a 1,000 pardons! I thought that I had used max characters before just a year or so ago and didn't research that. I should have, so I apologize.

Thank you for the test and the information. As usual, the FM Forums are wonderful! Thank you, Peter, and thank you, Ray.