>Store the date as an integer and then convert it into the correct date format by reading the regional settings of the workstation. See this link for the algorithm examples.
http://www.vsg.cape.com/~pbaum/date/jdimp.htmI took a look at that page and it contains a lot of things about that. I am not that much familiar with those calendars. I would have to look more into to better understand the concepts related to that.
When I adjusted the data structure in VFP to be more ready for a potential migration to SQL Server, I changed all date fields to datetime. That has help when I simulated packages to import my data to SQL Server. But, I didn't realize I would face an additional dilemna. For one application I am supporting, this is not an issue as they are dealing with modern date values. But, on another, I moved up several centuries in time and this is where I have some adjustments to make. I guess the best would be to adjust the VFP data structure now in regards to that, on that particular table where I am going that far in time, and the code in regards to it. Then, by the time I migrate to SQL Server with the package, I would be ready to have everything migrated as is and the code would be ready to go as well.
