Hi Eric,

>This may be a little elementary for this forum but we have a couple of Foxpro2.6 and Foxbase applications and are concerned about Y2K. What would be the main areas to focus? I have been told to Set Century On and change date fields to the appropriate length. Is that all there is to it?

Nope, there are other areas in your program that might be affected by changing SET CENTURY. For example, any string generated by DTOC() would now be 10 characters long, instead of 8. If you do string manipulation, you might get wrong results. You might calculations in the application that uses 2 digits only, you could have LUPDATE() in there, you might import data that has only two digits...

Check out my article in the March 1998 issue of FoxPro Advisor. It covers some of these problems. The article is available online on www.advisor.com, the program can be downloaded from CompuServe's FOXUSER forum. My solution requires some reqork in the code. Depending on how much and how proper you made use of teh Power Tools this can be widely automated (my beta tester needed a few minutes to make his application Y2K compliant). If you don't have the source code or you don't want to change it at all, check out Y2K on www.netlib.com. Unlike my solution it's not free, but it's even easier to incooperate and a quite impressive solution.

Christof