>Hi All,
>
>I've got two forms, one form launches the other on a button push.
>If I run the "parent" form from the project manager and launch the 2nd form, all is well.
>
>If I build my program (with many more forms and libraries) then run it and pop the "parent" form. When I launch the 2nd form, NOW I get a lovely error about "Unable to load file - Record 10
: Invalid Seek Offset", After searching the help file, I came across the entry for invalid seek offset. Ha Ha what a joke. (Call Microsoft Support)
>
>Well I guess my question is, what should I be looking for? I've nearly rebuilt the screen from scratch and this problems continues to exist.
>
I've seen several things cause this; in order of frequency:
(1) Frobbed index file - an index points to a non-existant record (happens most often when you PACK and forget to have all the indexes open or rebuilt.) or the ?DX is itself corrupted. Best fix - rebuild all indexes on tables from scratch.
(2) Frobbed memo file - a pointer in the .DBF points to an invalid position in the associated FPT/DBT. You need a file repair tool to fix this (FoxFix, DIRT, SDT Repair() method, etc.), and in all probability, at least one memo field content entry will be lost. Back up the table and any associated memo file and structural index file before trying to fix it, and in any case, you may have to go to a backup to get the old memo field contents.
This can also happen when a screen, report, project or whatever has a squirrelly pointer to the associated ??T file. If this is the case, your best chance of fixing it is with a file repair tool, opening it like a table. Back up as above, and pray - hopefully, youre using SourceSafe and can pull the last version and rebuild from there.
(3) Frobbed .APP/.EXE - rebuild the executable image.
(4) Soft File System damage - FAT Table, NTFS indexes or something similar jumped off a nearby cliff. Hope you have a backup. You may be able to correct it using something like Disk Doctor, but I wouldn't get my hopes up. Fixing the error with an operating system tool (SCANDISK under Win9x, CHKDSK /F under NT, run when the system is restarted) and restoring from backup is the most reliable fix.
(5) Frobbed VFP components. Reinstall VFP and reapply all patches afterwards.
(6) Pending hardware failure. The drive needs to have last rights administered; there's a hardware problem. A new drive and a good backup are
needed. If the drive is getting ready to die, make a backup and replace it - drives are cheap, work product is usually orders of magnitude more expensive than the media.
