Hi Kevin -

My experience w/INVALID SEEK OFFSET has always been the result of some sort of corruption w/the tables.

I would first try replacing the database container files(.dbc, .dct and .dcx) and if that doesn't help I'd read all my data into a brand new set of tables/indexes. Perhaps Stonefield Database Toolkit (www.stonefield.com) could help you.

Good Luck -
ellen whitney
EPS Software Corp
~ making IT happen ~

>Twice in two days at a new client site, this app has reported INVALID SEEK OFFSET and ERROR READING FILE messages when the app was doing a very simple SQL Select Statement.