I appreciate your effort and I thank everyone for your kind advices. So in the end I decided to use Win7 32-bit as long as possible, after all the 32-bit workstations with 3GB run more than fine.
![was there a foxpro 2.6 for dos? was there a foxpro 2.6 for dos?](https://images-na.ssl-images-amazon.com/images/I/51R97VMG5TL._SX218_BO1,204,203,200_QL40_ML2_.jpg)
The final published release of FoxPro was 2.6.
Was there a foxpro 2.6 for dos? software#
If you are converting Macintosh or MS-DOS files that have never contained. FoxPro was a text-based procedurally oriented programming language and database management system (DBMS), and it was also an object-oriented programming language, originally published by Fox Software and later by Microsoft, for MS-DOS, Windows, Macintosh, and UNIX.
Was there a foxpro 2.6 for dos? windows#
For variuos reasons the company didn't adapt/migrate their app, which, ironically, has been running even better under Windows XP (and 32-bit Win7) because the OS allowed new features like more reliable networking, distributed printing, email. The setup for the legacy app to work well in the virtualized environment was a bit cumbersome, the VM was slow, the support would be more complex. You can explicitly convert FoxPro 2.6 and Visual FoxPro 3.0 files to the. I support a company that has a very old, mission critical, FoxPro for DOS 2.6 (FPD) application. For the DOS applications, it is recommended the memory settings all be set to. That would require an additional license.īut the main reason is worse user experience and re-training. The last aspect is the shortcut to the FoxPro 2.6 DOS / Windows application. So unless there's something I don't know, I have to virtualize XP. Since the program got better with the features provided thanks to its ability to run under XP, these "services" must be retained (ie: networking, email integration). But I wonder if anyone can suggest a temporary alternative path, which doesn't involve either:Ī) downgrade 64-bit Windows to 32-bit, orī) run the app on a virtualized 32-bit XP You havent specified if this is FoxPro 2.6 (DOS) or FoxPro 2.6a (Windows) but either way I dont like your chances. I know this time the writing is on the wall: the only long-term solution is to migrate their app. Unfortunately for this company, most new machines now come with a 64-bit version of Windows 7, which is incompatible with their FPD app. I support a company that has a very old, mission critical, FoxPro for DOS 2.6 (FPD) application.įor variuos reasons the company didn't adapt/migrate their app, which, ironically, has been running even better under Windows XP (and 32-bit Win7) because the OS allowed new features like more reliable networking, distributed printing, email integration.