The reason for my problem was a regional setting in VFP. "Use System Settings" was marked. That leads to a default of "SHORT" for the Date Format. And Short (and Long) create errors when one tries to use a table with values like {^0209.20.02} or {^1071.10..03}. These are obviously typpos but are accepted with every Date Fromat other then Short or Long.
I removed the mark at "Use System Settings" and the errors are gone.
>Hi,
>
>I loaded the latest version from VFPX (2015-12-01) and upsized a VFP DBC but got some errors.
>
>For one table I get 33 errors. This is o.k. but: I can not look at the error information. Instead I get "Date/datetime evaluated to an invalid value.". I can not browse the table that seems to hold the error details.
>
>Tipps how to avoid that problem would be very welcome.
>
>Is there any documentation for the upsizing wizard?
>
>TIA
>Gerhard
Gerhard Schmidbauer
URANUS Software GmbH