We'd need to see the exact validation expression before we could suggest a solution. Perhaps you can copy and paste that to this thread?
Sure, I've switched the field names to just Date1, Date2 for ease. Dates 3 and 4 are set up the same way.
Date 1 calculation:
Date1 < Date2 or IsEmpty ( Date2 )
Date1 < Date3 or IsEmpty ( Date3 )
Date1 < Date4 or IsEmpty ( Date4 )
Date 2 calculation:
Date2 > Date1 or IsEmpty ( Date1 )
Date2 < Date3 or IsEmpty ( Date3 )
Date2 < Date4 or IsEmpty ( Date4 )
What is are the storage options for each of these fields? Are any of them a global field?
The idea I'm exploring here is that changes to a global field don't "stick" unless they are made on the host machine. Since you're now hosting these files from FileMaker Server, you no longer have access to a "host" instance of FileMaker unless you take the file down off the server and open it directly with Filemaker Pro.
Thus, if you accidentally uploaded your file with an unintended, different value in such a global field, you might get unexpected behavior when the validation executes. Of course, if none of these are global date fields, then forget everything I've just suggested. ;-)
Unfortunately none of them are global fields :(
Are any of the fields from a related table? And is that table in a different FileMaker File? If so, you might have an external data source reference that was valid on your local machine but is invalid on your hosted file.
If that's not the issue...
Sometimes a solution is easier to see if we break it down into smaller parts.
Modify your validation expression to just: Date1 < Date2
See if it works. If it does, add one part of the original expression back at a time until it fails, then focus in on the part that isn't evaluating correctly and see if there's anything different about it.
Ahh yes! Date 4 does reside in a related table, but that table is still inside the same FileMaker file.
I will remove Date 4 from the calculations and see what happens.
* * *
OK I tested it without Date 4 and still no dice. The validation appears to be happening at random. Sometimes when I enter an invalid date it will give me the error mesage, but most of the time it just accepts the invalid date.
BTW Thanks for taking the time to help me out!
Just thought I'd post an update:
I moved the Date 4 field from the related table to the same table as all the other dates, and it seems to have fixed the problem. :)