FWIW, I have a 2.6 App written for Windows 95, which then was run on Windows 98, and now on Windows 2000. It has been 'successful' with each migration. However, there have been a few glitches along the way that I've had to work around. One, each time we upgraded, the Office version also changed, and the application, which uses Word, sometimes didn't like it too much. I've also had problems in that the app wanted to use DOS-like file names, and with our network setup now, it doesn't like the UNC conventions. You should also be aware of the speed patch that's been mentioned here on some of the UT threads. IOW, the problems I've had haven't been W2000 problems, but problems with the way the app was originally written, changes to other software, and with our network setup (including the introduction of a Thin Client system). I'm currently re-writing it (as I learn VFP) to avoid all these problems, introduce new features, and bring the 2.5 App into the modern world.

>One of my clients is upgrading all of their client machines to Windows2000 from 98.
>They have a FoxPro 2.6 App that "supposedly" will not run on Windows2000 machines(I am told Win2000 does not support 16-bit Apps). Though the application does run on One of the clients Win2000 machines. Of course the solution would be to duplicate what the user did on the One machine that it does work, but that would be too easy.
>
>The proposed solution is to re-write the App in FoxPro 6.
>
>Can the 2.6 App run on Windows 2000 or will it have to be re-written?
>
>Thanks
>
>>> Wes