Best suggestion I can give you is to just try converting the screen sets (if you have them) to VFP8. We've had some experience with going from FPD/FPW 2.6 to VFP3 and found that you will average about 1/2 hour to an hour per screen, tweaking, etc. A lot will depend on how well the application was written in the first place and how well versed your people are in VFP.

Good Luck


>I'm playing around with the idea of moving old 2.x (DOS) code and recompiling it under VFP 8. The 2.6 stuff uses the standard @ SAY/GET syntax. While it works as-is under VFP 8, it's pretty ugly (even worse than the normal 2.6 screens). That's not really surprising, though. Anyone have any suggestions on ways of (easily) cleaning things up a bit? We're actually looking at just replacing the @SAY/GET stuff with VFP native forms but we could probably live with the SAY/GET stuff for a while if I could get it to at least look reasonable (ultimately, this stuff is just going to get completely rewritten).