>>What are the Y2K issues that apply to VFP 5.0?
>>
>>I do not want to upgrade to 6.0 & VFP 5.0 appears to be NON-Compliant.
>>
>>Any testing that I have done (with Set Century ON) does not reveal a
>>problem??
>>
>>Any comments...
>
>Microsoft lists VFP 5.00 as Y2K compliant. See Microsoft Y2k Product Guide Of course with any programming language poor programming can make the resulting product non-compliant. The MS webpage lists the things to watch our for.

VFP 5.0 does have some Y2K problems. LUPDATE() uses a 2 digit year. This has been fixed in VFP 6.0. Also, if you build dates from strings using CTOD, you may have problems. VFP 6.0 can help you identify these areas.