Missy,

The best solution seems to be a new product called Y2KFox. You just load it at the beginning of your application and it gives you the SET CENTURY ROLLOVER capability that VFP 5.0 has. This means you can set the rollover to 30 and any date with a year of 30 or lower will be interpreted as 20yy. Any year higher than 30 will be 19yy. It does handle 2/29/00 properly. You can get more info at http://www.netlib.com/.

Alternatively, the method you describe works well, but you have to add VALID code to every date field. There's an article in the March issue of FP Advisor by Christof Lange that describes the solution in detail.


>Hi Rick, I noticed you posted something yesterday for FPW 2.6, so I figured I would send you a question about Y2K and version 2.6.
>
>Any simple work arounds for Leap Year 2000? I know that the 'Invalid Date' message is displayed when the On Readerror fires, and I have a general idea of what needs to be done, but I am open for suggestions.
>An example I have seen is to copy the Leap Year date to the clipboard (using _CLIPTEXT somehow) and comparing it to the Julian Date for Leap Year 2000 (SYS(10, 2451604)and storing the 'modified date' back to the variable.
>
>I was just curious if there may be alternative solutions available. Any suggestions would be appreciated. Thank You.