Ken,

Perhaps there's inconsistencies between the actual DBF and fields definitions in the DBC, giving wrong record lengths?
Also, I noticed that you can't rename the actual physical DBF on disk.

I used to experiment with including DBFs and Tables, but concluded that there's too much inconsistent behavior in the results that I just abandoned the idea :-

Kenneth

>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