>I have just run across this problem in a commercial product I have out. it happened when my customer printed a report the report printed and was sent to the printer but this error popped up and there system froze, this is the only customer it is happening with. Microsofts online help was no help at all. told me to read developers guide chapter then call Microsoft. Any body have any ideas and what is a invalid seek offset any help would be appreciated.

I've seen this several times, always starting with a single computer then spreading 'outwards' across a network until everyone re-booted. In each case it was a hardware or driver problem: Once it was printer drivers (replaced HP5 drivers with HP4) the other times it was a bad network card or bad cabling.

Despite the MS information I've never found a corrupted index to be at fault.

HTH
Barbara