John,

This is a good idea if Calvin's main problem is screen and/or report real-estate. Of course the easiest is to just expand all date fields to 4-digit dates (which is what I did for my FPD 2.0 apps), but your suggestion should solve the problem where there's not enough room to do that.

Calvin, I would think that this would be a whole lot easier and quicker than porting the whole darn thing to VFP (unless, of course, you have other reasons for porting it and you were going to do it anyway).

Bonnie

>Hi Calvin ---
>
>Could you replace your dates with strings in the FPD app and write up some conversion and validation UDFs?
>
>How exactly does FDPD2.5 work with 21st Century dates?
>
>>I have a vertical market app written in FoxPro 2.5 for DOS. I had assumed up to this point that the Y2K problem would go away when the century actually turned over, in other words that if century were set off and a 21st century date were typed in the system would know that the system date was the 21st century and everything would be OK. Now, I ( am I the last idiot left ) find out that FoxPro DOS itself is locked into the 20th century. It does not recognize the 21st Century system date. I now understand why Microsoft is being sued over this. Why have they not provided a patch for this problem. I am in the process of moving users to a VFP version of the product but they may not chose to convert. They may instead chose to sue us for selling them a product that does not even know what century it is in. I forsee a large number of law suits directed against Redmond if they do not fix this problem!