>>
>>i'd leave it in 3.0 and let them suffer under win32 until they're hardware is approved. much easier this way, and easier to port up to the next level when they're ready...
>
>For what it's worth...Most stuff I've developed in VFP is running
>in Win 3.x utilizing win32s. I have had virtually no problems with it.
>
>Good Luck

I agree that leaving the app in 3.0 would be easier, but there are some politics going on here. This is a fortune 500 company that mandated to all department to be up for NT by 1/97. So we've been working on porting our old DOS based system to into 3.0 and beat them to the punch so to speak, and of course, not the hardware aquistions are being delayed by up to a year and some of the users, while on 3.11 are also on 386 machines (even one SX) and the 3.0 app is painfully slow. They decided they cannot live with that are asked for our suggestions and, after all, they pay the bills. We wrote a list of recommendations to them (one of which was living with 3.0 -- it works, but it's slow and some of the 32 bit screen controls can be flaky at times). But they decided to pay us to develop this 2.6 "patch". So, you see, the choice isn't really mine.

- Rob