>>>>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.
>
>As the difference in replies points out, as well as the fact that your corp. has a list of what's compliant which disagrees with M$' list, the problem with this sort of question is the related question: "what did you mean by compliant?"
>
>There are
many issues which are on the list of problems caused by Y2K. Some of them are trivial things no one may care about except to get a product they don't like on a list of non-compliant programs. Some of them could potentially bring a mission-critical app to a grinding halt and stop a large business from operating (or at least make it difficult).
>
>You have to learn more about what the specific issues are, and find which ones your clients do and don't care about (some are appearance-only), and decide for yourself whether a product (or an old app you're renovating) is, or can be made, Y2K-compliant to the satisfaction of the users.
>
>HTH,
>Rich.
That's a good point. Just to extend that a bit...just because VFP is "compliant" doesn't mean the application you create with it are compiant.
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer