>>Wait a minute!
>>
>>I believe Dmitry says there are only 100 rows in this DBF and he says he pulls the whole thing into a cursor.
>>
>>Solution: REMOVE THE INDEX.
>>
>>You really don't need an index or indexes on a table that small. FoxPro will suck the whole table into memory in a heartbeat or two.
>
>My first step is enclosing the SQL Select with TRY CATCH (so that the application does not crash).
>Then, if I get no errors, I will forget about this issue (and move on to the next one :)).
>But if I still get the problem, even after TRY CATCH, I will remove the Index file. You are right, 100 or less records in the EXE should be no problem for VFP. Unless Invalid Seek Offset is caused even when Selecting/Opening a DBF. Nobody but VFPT know what caused the ISO error. We are just guessing that the index file is in the problem.
>Thank you.

Ok, I actually did work at Microsoft in the FoxPro group and have been working in xBase since 1982. Sure, at Microsoft I was just the developer of the automated testing system written in VFP, but I know what an Invalid Seek Offset is and it almost always has something to do with the CDX or the IDX and the fix always seems to be a reindex or better still a drop of the index file and a recreate of the index.

Again, in your case you have so few records that performance will not matter.

And is this the table you've embedded into the EXE? And it's some kind of static config table or something?

If this is the case, I think you're just wasting your time on a strange once-in-awhile bug that has no explanation. REMOVE THE INDEX and be done with it.