What about in a situation where you store the system date to a variable such as: Replace dToday With Date()
Where the Date is 01/05/2000. This stores the date, in the table, as 01/05/1900. Currently, this application does this type of date saving throughout the application. I have no problems with dates that users must enter. These fields are all four characters wide. In addition, I have placed Set Century On in the main program. I have not tried your latest suggestion yet, however, I will this weekend.

Jason


>Jason,
>In your config.fp(w) add "century=on" and increase all your date entry/show fields on screen to 10 char width. So a date in 2000 could be entered/showed as 01/01/2000 (still stored 8 bytes YYYYMMDD format internally - slashes are just part of inputmask).
>Cetin
>
>>Hi Cetin. Thanks, once again, for your advise. I should have restated my question better. Currently, the app. I am dealing with stores dates in the database as 05/27/98. The data type is, of course, Date which has a length of 8. I moved the system date forward to Jan 1, 2000 and entered some data to the app. I then checked the date in the table's field and it was stored as 01/01/19. This is what I see as being the problem. It there a way around this? I don't have any manuals to reference, thus that is why I post my question on the Thread.
>>
>>Thanks,
>>
>>Jason
>>
>>>>Could someone please tell me the difficulties in converting a FoxPro 2.6 for DOS version so that it's Y2K compatible? What code has to be included? Etc.
>>>>
>>>>Thanks
>>>Hi,
>>>I'm not sure I completely understand this one. DOS version (all versions from foxbase) is also Y2K compatible. All FP tables store the date as YYYYMMDD internally. All you need is to set century on and use 4 digit for year.
>>>Cetin