Has anyone experienced the date separators of a Date/Time field becoming corrupt after a Design Refresh?
Consistently one field gets corrupted. It is defined as Custom, show=Only Month, day and year; Special=Always show 4 digit year; Calendar=Gregorian; Format=WDMY; Separators= space / /; dd mm yyyy ww.
But after a Design Refresh the field has D M D as separators. Correction - we’ve now established that the Field in the Template gets corrupted, which obviously trickles through to the databases that use that Template. It seems that just editting and saving the Form can corrupt the field, but not every time.
I’ve searched the fix database, these forums and googled to no joy.
Your suggestions welcomed, as we’ve had this problem so long that we’ve now coded an onLoad event to replace D’s and M’s with slashes.
This is a new one for me, and if you could pin down the circumstances in which it occurs so that we can reproduce it, then we could have a look at it here.
Thanks Andre - if you’ve not come across it before then it must be something specific to us and the field.
The same field occurs across 3 Templates - more than likely each field came from a common ancestor way in back in V1 of the database, which would have been around R5 days. We’re now on V3 of the Templates and running 6.5.1 on the server and 7.0.1 clients, though we’ve have had this problem for an awful long time across different platforms and clients.
I’m sure we have deleted and recreated the field before, but it’s worth one more try I suppose.
Is it common to use “Custom” format for Date fields? We do it in order to force an international set of web users to stick to a standard format.