well - in this case - the error is:
1) reproducible
2) eliminatable (I hope that's a word)

Simply by closing the table in one datasession before the reference to it in the other, the problem vanishes - undo the close - the problem re-appears. I sdon't have the time to track this down to specific conditions, but hey - it worked for me!

>Ken,
>You're not going to like this answer and I have to admit I have yet to find one person to agree with me.
>I have been seeing the Invalid Offset Seek error message for the better part of a year using VPF 5. It rears its ugly head whenever it want to at the DO command. This could be a DO someprg command at the command window or a DO procedure in an already executing program. In my case it has nothing to do with DBCs, tables, indices, etc. It could occur in some housekeeping program who's only function is to set a default directory, that is, no tables in use. Also, after receiving the error, if it's in response to trying to run a program from the command window, if I make a second effort at running the program the Invalid Seek Offset problem will invariably not show up and the program will run normally. I am firmly convinced that it is a symptom of bad memory (the computer's, not mine :-) ). It started for me when I put some additional ram into the computer. It's a pentium pro 200, by the way. On system startup the bios does a memory check and finds no memory errors though that's a
>cursory check, at best. My question to you is have you changed anything involving this computer's memory before the ISO error showed up?
>Good luck with what I'm starting to call an condition, not a disease. I've learned to live with it.
>-Dore
>
>>Ok - I seem to have found a behavior that causes an "invalid seek offset". Basically - although I haven't thouroughly tested it - the following sems to be true:
>>
>>If you have a free table (.dbf) included in an .EXE - trying to use and reference a field from that table more than once at the same time - ie in different datasessions - causes an "Invalid Seek Offset" error.
>>
>>Can anyone confirm, deny, or otherwise elaborate on this? It took me half the stinkin' day to find this since I wasn't getting the error in VFP (where the table is just a dbf file) but kept getting it in the EXE where it is included. This is a real "gotcha "- or at least, a real "gotme" :-) would love to hear more on this if anyone knows TIA-Ken