>There is more info available on this new behavior at
http://support.microsoft.com/?id=814131. The suggested fix for the problem in that article uses ALTER TABLE rather than PACK, as it doesn't depend on the presence of, or remove, deleted records.
>
>You can turn off the checking (and emulate behavior of past versions) with SET TABLEVALIDATE, but I wouldn't recommend that.
>
>The fact that a particular 3rd party product doesn't detect or fix the condition should be brought to the attention of the developer of the 3rd party product.
Jim,
I think, that
A problem occurs when an insert or an append operation causes a table (or .dbf) file to exceed the 2-GB maximum file size. The problem causes the following error:
In earlier versions of Visual FoxPro, trying to open a table in such a state causes error 15, and you receive the following error message:
Not a table.
In Visual FoxPro 8.0, the action that would have caused the table to exceed the maximum file size, causes error 1190, and you receive the following error message:
File "name" is too large.this error message could be improved further. It can be more explicit about the actual cause of the problem.
If it's not broken, fix it until it is.
My Blog