If you need to maintain legacy FoxPro 2.x applications in today's changing environment, your primary concern will be keeping your app running smoothly on newer operating systems and hardware platforms. A FoxPro application that has run perfectly well for many years may unexpectedly crash tomorrow when it is run on an upgraded machine.

The reasons for this behavior are easy to understand -- FoxPro was originally written as a 16 bit DOS program. In 1993 it was ported to a 16 bit Windows 3.x application. The "average" platform of that era was a mixture of 386s and 486s, with clock speeds between 33 and 66 MHz. Hard drives bigger than 500MB were still a rarity. As these machines got upgraded to Pentiums, with CD-ROM drives, multi-gigabyte hard drives, network drive mappings and blazingly fast processors, certain problems started to appear in FoxPro. There are several well-documented problems in this area, and also some well-documented solutions. This survival guide will provide you with all the information you need to keep your 2.x apps running smoothly on a wide range of modern platforms and operating systems. Some of the more important issues facing FoxPro 2.x developers are:

WinME: Insufficient File Handles

Upgrading FoxPro 2.x

Running FoxPro 2.6 Applications in Windows 95

Error: Divide by zero (Windows only)

Error: Insufficient memory

Error: Cannot read from drive D

Error: Position Off Screen (Windows only)

Y2K Issues

Known Bugs in FoxPro