I have made short reply to Ed Rauh, because his one was actually oversimplification. I would expect to speak, if necessary, with Ed about this, not with you. Anyway, if you have to drop some insight to a thread, you may feel free to address the person who asked a question. George, as I understand, says that FPW app is mostly, to the extent of developer's skills, compliant, and I expressed, though briefly, the same idea.
Whatever, you see on UT, you still have no grounds to bold some words underscoring your doubts about anyone's credentials.
Anyway, there is certain circle of people here, who are very aware about your and mine skills, reputation, personality etc.

>George's response has a lot of insight. However, in many cases, set century on is not enough. To say "just by setting century on", which you did, is an oversimplication of the process. George's response is George's response, not yours. It had a lot of insight, and clearly, he put a lot of thought into it.
>
>I am not sure how George's response has bearing on your 1 sentence response that was an oversimplification of the issue....
>
>>This is not personal, but your previous reply was. You may look at George's message. It will explain you the case, if you want to know details, though the conclusion will be the same.
>>
>>>Ed...
>>>
>>>It is not a personal attack. You simply cannot make an existing FPW 2.x Y2K compliant just by setting century on. IMHO, you have over-simplified a situation.
>>>
>>>How is this personal???
>>>
>>>>John.
>>>>
>>>>When will you stop to mix technical issues with personal attacks?
>>>>
>>>>>Ed...
>>>>>
>>>>>Your response: or just by using SET CENTURY ON
>>>>>
>>>>>The statement you responded to:
>>>>>
>>>>>FPW is not Y2K compliant without significant recoding or the addition of third party products such as Y2KFOX
>>>>>
>>>>>Regardless of what you say....you are not only NOT accurate, you have over-simplified what can be at times, a complicated situation....
>>>>>
>>>>>
>>>>>
>>>>>>It entirely depends on how application was designed, mostly on how careful DTOC was used. There are plenty of FPW applications that are fully compliant.
>>>>>>
>>>>>>>That DOES NOT make an app Y2K compliant...<s>
>>>>>>>
>>>>>>>>>>I need to provide justification, to a customer, for rebuilding an application in VFP. It's currently in FPW26. Aside from the usual benefits gained in performance and functionality, I'd like to explain the pro's and con's from an environmental standpoint.
>>>>>>>>>>
>>>>>>>>>>Anyone care to contribute?
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>FPW is not Y2K compliant without significant recoding or the addition of third party products such as Y2KFOX
>>>>>>>>
>>>>>>>>or just by using SET CENTURY ON