>Ever since we released a new version of an VFP exe that was upgraded from VFP6 to VFP9SP1 some users are getting various Error#2034 "Date/DateTime evaluated to an invalid value" errors. Some when trying to rebuild indexes, some while using the application running a sql statement that does a DTOC() of a value in a free FoxPro 2.6 style table. We are unable to reproduce it. These are the code that may affect it as we are letting VFP take whatever the windows date and currency formats are with these lines
>
> SET ENGINEBEHAVIOR 70
> SET STRICTDATE to 0
> SET SYSFORMATS on
>
>Seems like at least hearing from one of these users they are probably running windows XP and have the settings of
>
>Short Date 7/8/2009
>Long Date Wednesday, July 08, 2009
>Short Date format mm/dd/yyyy
>Long Date dddd, mmmm/dd/yyyy
>
>in Regional Settings and Formats control panel
>
>Any suggestions on internationalization gotchas in VFP and workarounds as far as dates?
>
>Thanks ahead of time for any suggestions or advice!
>
>From: Ed
Ed,
How you're inserting / updating dates? Can you use strictdate format as
{^1999-01-01} ?
If it's not broken, fix it until it is.
My Blog