Using VFP6 with latest VS SP

I've been trying to run some legacy code for the last 2 days that uses a SCAN/ENDSCAN to make static copies of two tables. (One of those two tables, the child table, is over 300,000 records). Fairly simple code, could be done with just SQL Select but this code needs rewritten for the next version of this app... I didnt want to rewrite a simple routine now when it will still need done in the future, and hey it always just worked.

The code scans the parent table to find applicable records. When it finds one it stores that record to the new static copy of the parent table, then uses a foreign key from the record to SELECT records from the large child table. It appends those child records to the 2nd static table, and cruises on.

It's crashed twice now (in two different places in the SCAN loop, but same line of code) on the Append of child records with "Invalid Seek Offset". I'm not exceeding file size limits but I am running this across the LAN (like it has always been run). When I go to look at the static child table, the last record appended has gobbly gook characters sprinkled throughout the fields, and as soon as I try to navigate off that record, WHAMMO! C5 Error! (program execution was suspended at the time) The table is of course corrupt after this too.

The only thing different from the last time this legacy code routine was run is that the recent VS SP and VFP COM update is loaded. It was run in VFP 6 once before with no problems at all that I know of.

Have I rung any bells with anyone? I'm going to kick it off again to run overnight (and cross my fingers), then if all else fails rewrite it with all SELECTs tomorrow.