2099

[sopomeres]

CR v8.5: When pulling a date from a FoxPro db, the year "1999" is appearing as "2099". Any ideas on how to fix this???

Thanks.
Chuck

 

[MrBillSC]

It sounds like the foxpro db is not storing the century so Crystal is assuming the current century.
If your foxpro records do not have future dates, you might create a formula that compares the record date with Today. If it is a future date, change the century to "19".
Ideally, it would be good to store the century in the foxpro database. If it is in the foxpro db, I don't have a clue as to why Crystal can't read it.

MrBill

 

[Mike Lewis]

MrBill,

Sorry to disagree with you, but Foxpro always stores the full century with the date (and always has).

Chuck,

Does the problem occur will all dates, or is it just 1999 that gives the problem? Also, how are you accessing the table -- through ODBC, OLE DB, or natively?

Mike




Mike Lewis
Edinburgh, Scotland

My Visual Foxpro web site:

http://www.ml-consult.demon.co.uk

My Crystal Reports web site:

http://www.ml-crystal.com

 

[dgillz]

I doubt very seriously that Crystal is doing this. Please open your FoxPro database in Excel and let us know what the date looks like. Be sure there are no formatting options set in excel when you do this.

Software Sales, Training, Implementation and Support for Exact Macola, eSynergy, and Crystal Reports

http://www.trianglepartners.com