>>One of my clients is upgrading all of their client machines to Windows2000 >from Win 98.
>It very nice, this means that he has enough money to order you new VFP version
>>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).
>This is not thrue. Win 2000 could suppot 16-bit application, but you can't gain from USB support and will have some printing problems. In reality XP doesn't support DOS apps

That's flat-out wrong; I've used XP successfully with DOS apps and Win16 apps; in a few cases, the app needed to run in an emulation mode.

>>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.
> Not FVP6.0, better solution is in VFP7.0.

In what way does VFP 7 specifically address issues with XP better than VFP 6 AFA porting FPDOS code?
>
>Can the 2.6 App run on Windows 2000 or will it have to be re-written?
>My personal advice is: using situation force your customer to pay you for new VFP advane. World go to OS without DOS and now is time to make convertion of the prodicts.

FPDOS and FPW 2.6 will run under Win2K; some Y2K issues continue under Win2K, but third party software such as Communications Horizon's Y2KFOX address these well. You are faced with issues around share and printer naming and device mapping, but these problems were there even under Win9x.

>Last two years we make more than 10 conversation of old FP apps in VFP&SQL, acting as a outsourcing center. Our partners support their previous version, while we build for them new apps.