>I was wondering (and I am sure that some of you must know) why exactly MS puts a 2 gig limit on the size of VFP tables. We are quickly approaching this limit on one of our tables and it has forced us to move the app over to SQL Server. Hopefully there is a better reason for Microsoft limiting the VFP file size other than trying to get VFP apps to migrate to SQL.
>
>I am experiencing the frustration of watching my app lose performance as I "upgrade" to a client server solution.
>
>Anyone know why there is a 2 gig limit, and does anyone know why MS hasn't ripped Rushmore out of fox and put it into SQL Server yet?

From Jim Booth on this subject:
---------
Yes the 2GB limit is still in VFP 6. That limit is not involved with the OS at all (although it began because that was the OS limit). The limit is involved with teh locking scheme that is used by VFP and changing that would render a new version of VFP uable to coexist with older versions sharing the same data.

----------