>>Hi,
>>
>>The core application for my company has been written piece-by-piece over the last three years, by the owner... in FP DOS 2.6...
>>
>>Now it's got to be made Y2K compliant.
>>
>>I've read the reviews on Y2KFOX and it seems like it would be just the ticket. The plan is to re-write the application in VFP, but this would get us over the millenium hump.
>>
>>Has anyone used this product?
>>Does it perform as advertised?
>>How's the support?
>>
>>It sounds almost "too good to be true"... and you know what that means ;)
>>
>>TIA
>
>Larry,
>
>It sounds like you are in the same spot I was in 10 months ago. The application I inherited was originally written in DOS, moved to 2.6 and patched to death.
>
>As it turned out, the Y2K compliance was the least of my problems. Y2KFOX makes it a no-brainer. All I did was install it and add the .exe to the command path (d:\winapps\usttrack\y2kfoxw.exe /a25 d:\WINAPPS\USTTRACK\USTrack.EXE). We also opted to 'set century on' so the field sizes needed to be changed and I am still struggling to get the users to enter mm/dd/yyyy date format. You may also encounter some gotcha's with left() and right() manifestations of weird date manulaptions and calculations but absolutely no problems with Y2KFOX.
>
>It really is that good and that easy. As for support, I haven't needed any!
>
>Keep in touch - let me know how it goes.

Bob,

Thanks for your prompt reply. I'm likin' this approach more and more...

One question, our app is *not* compiled as the owner likes to be able to "tweek" it occasionally. Will Y2KFox work with a .prg / .fxp file just as it does with a .exe ???

Thanks again