Error: “invalid seek offset.”

This can often be corrected simply by restarting BarScan.  Next, since this error is detected while accessing an index, a Table Integrity is recommended.  Note that if the index issue is serious an you cannot log out of BarScan, you may be required to use Windows Task Manager to end the BarScan application.  Then start and login to BarScan as you normally would.  Do not open any tables, but immediately from the Main Menu select File-> Company-> Housekeeping-> Table Integrity, make sure that the company with the issue is highlighted in the list and then press OK at the bottom of the list.  Once completed, the error “invalid seek offset” should no longer occur.

BarScan uses Microsoft Application Code to power its data access.  Microsoft users encountering this error have stated that is has been caused by either:

(1) network connection issues, such as heavy activity on the server or slow network throughput,
(2) printer driver problems,
(3) hardware problems on the workstation or some issue on the server.
(4) antivirus activity.
(5) users turning off the computer, killing the application, or losing power while application edits are pending.
(6) network server’s read/write caching not behaving correctly.

In other words, it appears to be BarScan’s reaction to corruption caused by some outside event, program or driver stomping on data, network traffic or memory.  Most of the above listed items will produce only intermittent problems.  Some have replaced third party printer drivers with the equivalent driver from Microsoft and seen the problem disappear.  Some have seen the problem disappear with the next antivirus update, after replacing network cards, or by avoiding work at times when they know the server is in heavy use.

In summary, do a Table Integrity on the affected company and take careful note of the exact circumstances under which it occurs if it happens again.  This will help track down the source of the issue, which is likely to be one those listed above.