Thank you for your post.
This issue has been previously reported. In essence, when a file is created in a different language/locale, then when the file is transferred to another language/locale, the value list uses the date format from the original language/locale.
You can view posts from other customers experiencing the same issue at:
I have attached your post to the original report, and I will contact you when any information becomes available.
One workaround is to change the default language to Unicode.
Thanks TSGal. The difference between this situation and some of the earlier posts is that my value list problem does not involve related records. This is a value list based on a field in the same table. Also, the file was not created and has never been used other than with Australian settings.
I have encountered this bug too, in my case it has nothing to do with the relationships or what format the file was created in.
Steps to recreate
Install FMP12 on Mac OS 10.7.3 set to UK system format (DD/MM/YYYY).
- Create a new database
- Add a date field (which it automatically sets to UK format)
- Add a few records with dates in format DD/MM/YYYY
- Create a value list, source - date field
- Assign the value list as a drop down on a test field)
- Dates in value list will be MM/DD/YYYY and will throw an error when selecting due to invalid date format.
Create two new fields: -
DateAsText = Calculation, result=Text, Formula: date (gives us the date in UK format, but is treated as text, not a date)
DateAsNumber = Calculation, result=Number, Formula: date (will return the day number since the year 0000 - we use this to sort the records in the right order)
Now edit you value list which references the date field and change it to reference the DateAsText field, and add secondary values from DateAsNumber, sort by second field, do NOT hide first field.
Now your drop down will show: -
- 30/04/2012 734624
- 07/05/2012 734630
Its fugly but it works and will just drop the actual date (in the correct format) in to the field.
FMP12v2 where are you? Any eta?
Following up on my earlier post.
I just did the same using FMPA12 on Windows 7 64 bit. Just like on the Mac Version, I created a new database and my computer is set to UK English.
As before, the value list displays as US format but the field displays (and needs input in) UK format.
Thank you for the additional information.
The Testers have informed me that this issue is known to also occur with any drop-down value list based on any field in any table.
Thank you for your posts. I have also attached your posts to the original report.
FileMaker, Inc. does not speculate nor discuss future products.