>Is there anything else to do in VFP when dealing with a large amount of data that exceeds the 2 GB limit (besides using another database as the 'back-end') ??

Steve,

A few things come to mind. The first is data partitioning. Data partitioning is the act of breaking one physical table into two or more physical tables while still maintaining the same logical design. Partitioning can be done either horizontally or vertically.

Horizontal partitioning is dividing the fields into two or more tables with a one to one relationship between them, while vertical partitioning is dividing the records between two or more tables based on a sort ordering. For example, in an Employee table horizontal partiitoning might be accomplished by placing demographic fields in one table with other fields in another. Vertical partitioning would be accomplished by putting employees with names beginning with A to M in one table ant those with N to Z in another.

The second thing that comes to mind is that very often a situation where a table becomes so large may be due to a design flaw. Perhaps one table is really trying to do the work of what should be many tables.