Graham, Usually index corruption or a corruption of the DBF header. Normally copying the data to a new table then zapping and appending back cures the problem. The cause of the corruption I most often found was network timeouts caused by cheap network cards or switches.
Dave -----Original Message----- From: ProFox [mailto:[email protected]] On Behalf Of Graham Brown Sent: 14 January 2014 10:05 To: ProFox Email List Subject: Invalid seek offset Hi all One of my clients has just started getting invalid seek offset errors. The app is vfp8/codemine8 with a SQL 2005 database. I'm just trying to pin it down to see if it is antivirus or power saving etc. Also asked the hardware guys to see if anything appears in any of the log files. Has anyone come across a definitive reason for this error? Regards Graham --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html --- [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
