>The only reference to 12/30/1899 that I have found when searching VFP help files concerns date time functions when a date is blank. Other than that, the only reason that I knew about it is from testing and from posts here. I don't know the significance of 12/30/1899, but in VFP tables accessed via ODBC, this is the date that is entered as the default when a date is blank. In SQL server it is 1/1/1900. I think that it is also 1/1/1900 for Oracle but it has been a long time since I checked and I cannot say for sure.

I think I read somewhere that VB (or is it Excel) has two starting points for dates, with one perhaps being obsolete, but I'm not sure.


>In my applications, I support VFP, SQL Server, and Oracle. The user is free to choose which database thay wish to use. All remote views are tested against each of these databases. Other DBMS may work, but so far these are the only ones that I currently support. Due to inconsistancies in data types between difference DBMS databases, I normally only use character, numeric and integer fields and do conversions in code and on reports to properly display and query data. Probably not the best data storage solution, but it makes my code work for each database without having to know what data source I am working with.

Interesting approach. How do you handle stored procedures?

Alex