>I tried the suggestion, setting both foreground and background memory to half a gig, but the program crashed just the same. The frustrating part of it is that it got to nearly 20,000,000 records (and 2-3 hours) before it crashed, and it turned the table to which it was inserting records into toast again.
>
>The message this last time was the infamous "Invalid Seek Offset"; the help file's instructions when getting this one, say only to "Record your recent actions while using Visual FoxPro and then call Microsoft Support."

In my expirience the "Invalid Seek Offset" error is caused either by table/index/memo corruption or a network error.
BTW, what's the size of the table you're adding to? Is it close to 2GB limit?