Thank you for the post.
Knowledge Base article 9710, Mac OS X Lion compatibility with FileMaker 10 and earlier and Bento 4.0.5 and earlier will shed some light on this issue.
"When formatting dates, the year may show incorrect dates with Asian characters."
While these earlier versions may install and run on Mac OS X Lion, you may encounter installation and stability issues for which there is no resolution. We strongly recommend you use current FileMaker software.
I can use customized formatting ok. The pre-set date formatting does not work properly.
I'm a small (but frequent) user of FM Pro and can't justify expense of newer versions!
Is it certain this problem does not exist in latter versions?
Thanks for the advice anyway.
Thank you for the reply.
The following knowledge base article 9901 lists the known issues with Mac OS X Lion:
We do not list the date formatting issue for either FileMaker Pro 11 or FileMaker Pro 12. If you wish to test with your database file, then the free 30 day trial of FileMaker Pro 11 and FileMaker Pro 12 are located below:
I think I may have the same problem.
Have tried the link suggested above but that doesn't solve any of my problems and seems to lead me around in a cirlcle.
I have noticed that just recently on my Filemaker 9 It is outputting some strange characters (Japanese ?) in a date field
Another date field though seems to be fine.Everything else on the template looks OK and I can't understand why it should suddenly do this.Any thoughts ?I am running Mac OS 10.8.4There must be a work around surely.It seems ridiculously expensive to upgrade to Filemaker 12 (300 dollars !) when everything else in the database works well.One expects good software to continue to improve not simply stop doing basic functions.
Think I have found a workaround myself:
In Layout mode clicked on the bad field (the one showing Japanese characters where the year should be.
Right clicked on this field (Ctrl click) and selected "Date Format from the list.
It was set at "Leave date formatted as entered"
Reset it to Custom and filled in the details as they should be ie.
That seems to work
Hope that may be of help to you too.
Digby mentioned the best workarround for this known issue.
If updating to newer versions is a option, I'ld recommend latest FM11.
I started with FM12 more than 1 year ago and I still regret. As of today, still some annoying bugs not resolved. Lack of performance, rendering issues, …
Digby's answer works so I'm happy to get back to business, but I'm joining the others who find FM's "just get the upgrade" response a poor one.