foxproquery
Programmer
How do i convert a 16bit foxpro 2.6 program to 32 bit environment, so that it will be compatible with all forms of windows?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
conversion from 16bit environment to 32bit
- Thread starter foxproquery
- Start date
- Status
I've written before. It is so easy to say re-write it in VFP because of all of the benefits, but if there is little money to pay to reinvent a system that currently works, it seems to me that it makes sense to take the existing .spr, .mpr, .prg, etc. files and recompile them using VFP.
I support several applications that were written in 2.6 and have been recompiled with VFP6.0 with improvements in both functionality and stability without reprogramming everything. I admit that it would be more fun if they were in native VFP code but the bottom line is that these customers are not willing to pay for fixing something that isn't really broken.
Check your 2.6 code for long variable names which 2.6 agnores but VFP will treat as written. Also, reports may need to be adjusted to keep detail bands from overflowing. VFP is also touchy about dates. Look at the strictdate setting.
Good luck
I support several applications that were written in 2.6 and have been recompiled with VFP6.0 with improvements in both functionality and stability without reprogramming everything. I admit that it would be more fun if they were in native VFP code but the bottom line is that these customers are not willing to pay for fixing something that isn't really broken.
Check your 2.6 code for long variable names which 2.6 agnores but VFP will treat as written. Also, reports may need to be adjusted to keep detail bands from overflowing. VFP is also touchy about dates. Look at the strictdate setting.
Good luck
While the MS "assisted" conversions from FP to VFP are one way to approach an upgrade, most everyone will tell you that it's better, in the long run, to do a rewrite. The most useful information I got on migrating, came from MicroEndeavours, Inc. They have a self study course VF610 "FoxPro 2.x to Visual FoxPro Migration Manual" choose "Self-Study" at the left, then down near the bottom of the page.
This includes a number "why's" and "how to's", as well as some useful utilities to assist in the process. One of their techniques allows a gradual transition using a mixed model, but there are some downsides as you might expect. Also, one utility can create forms from the running code - you don't even have to have "screens" (.SCX files) to convert them. For the price - $249 that last time I checked - you can't get better advice. (I have no connection with them, other than being a satisfied customer.)
Rick
This includes a number "why's" and "how to's", as well as some useful utilities to assist in the process. One of their techniques allows a gradual transition using a mixed model, but there are some downsides as you might expect. Also, one utility can create forms from the running code - you don't even have to have "screens" (.SCX files) to convert them. For the price - $249 that last time I checked - you can't get better advice. (I have no connection with them, other than being a satisfied customer.)
Rick
- Status
Similar threads
- Locked
- Question
