I am running an application in MS-DOS Foxpro 2.6 without problems. I have the source code and with a lot of brute force, from time to time, I modified it to suit. I recognize that sooner or later hardware and software support become problematic. From a "computing" and backward compatibility point of view, the program works seems to work fine with VPF 5 except a few issues. The screen display and printing issues.
1- The screen shows different size fonts even a statement is added at the begining of the program to SET SCREEN FONT TO "courier",10 or foxfont. In particular, screen writes are in ok but the menus are boxed with a smaller size font. Though "workable" it's very annoying visually. The DOS version has the backgrounds highlighted (which suits me just fine). I have some understanding why this happens regarding Foxels. Is there a routine that I can run in the beginning of the program so that VFP will "mimick" an old fashion 80x25 screen. I don't care about scalability or frills just reasonable readability. (This is a billing program to collect money. I don't care about bells and whistles and beautifying my neighborhood with beautiful screens shots.)
2- Printing with the DOS version typically is designated with @2,10 SAY "blah, blah, blah" etc. How do I mimick the DOS version line printing. Font sizes are different and problems occur with preprinted forms arise.
3- When running the program with VFP 5, the databases are modified and then no longer recognized by the DOS version. I assume a header is being modified. How do I tell VFP to leave the databases in "DOS" format. (I really won't care if someone in Tibet can't process my dbf files.)
4- The DOS version of my application was originally preferenced because a lot of work is done remotely. Sorry Windows lovers, but, sending just screen updates in a DOS pcAnywhere session beats the living daylights out of any graphical screen over a 28k connection. (Screen updates are so fast that I sometimes have to double check to check whether I am online or working with a local "work" copy of my application. Any solutions? (aside from suggesting that I either live in my office or use a DSL line that Bellsouth won't make available until the year 2025)
Addendum:
Too bad Fox Holdings was squeezed and sold out to Microsoft.
1- The screen shows different size fonts even a statement is added at the begining of the program to SET SCREEN FONT TO "courier",10 or foxfont. In particular, screen writes are in ok but the menus are boxed with a smaller size font. Though "workable" it's very annoying visually. The DOS version has the backgrounds highlighted (which suits me just fine). I have some understanding why this happens regarding Foxels. Is there a routine that I can run in the beginning of the program so that VFP will "mimick" an old fashion 80x25 screen. I don't care about scalability or frills just reasonable readability. (This is a billing program to collect money. I don't care about bells and whistles and beautifying my neighborhood with beautiful screens shots.)
2- Printing with the DOS version typically is designated with @2,10 SAY "blah, blah, blah" etc. How do I mimick the DOS version line printing. Font sizes are different and problems occur with preprinted forms arise.
3- When running the program with VFP 5, the databases are modified and then no longer recognized by the DOS version. I assume a header is being modified. How do I tell VFP to leave the databases in "DOS" format. (I really won't care if someone in Tibet can't process my dbf files.)
4- The DOS version of my application was originally preferenced because a lot of work is done remotely. Sorry Windows lovers, but, sending just screen updates in a DOS pcAnywhere session beats the living daylights out of any graphical screen over a 28k connection. (Screen updates are so fast that I sometimes have to double check to check whether I am online or working with a local "work" copy of my application. Any solutions? (aside from suggesting that I either live in my office or use a DSL line that Bellsouth won't make available until the year 2025)
Addendum:
Too bad Fox Holdings was squeezed and sold out to Microsoft.