>>I have converted my app to SQL Server database. So this has eliminated the corruption of the application DATA. But my app still, on occasion gets the "Invalid seek offset" error. The error happens when the application tries to access/open/load meta data which is still in the DBF format. I believe that "Invalid seek offset" is caused by some kind of PC memory corruption (be it from a buggy printer driver or some other).
>>
>>But I am thinking; what if I replace all my meta data tables from DBF to XML format. Will it eliminate this "Invalid seek offset" problem? That is, do you know if the corrupted memory is only causing the problem when opening DBF files? Or any file(s)?
>
>IME ISO errors have been caused by network or local file system reliability problems - cabling, switchgear, server, power failures, computer crashes etc. Short-term solution for me has been to reindex, preferably after replacing suspect CDX files with known good ones (so that tag information is known to be correct). In the longer term, address the reliability issues - look at Windows event logs etc.
>
>The Wiki article at http://fox.wikis.com/wc.dll?Wiki~InvalidSeekOffsetError1103~Wiki seems to think this error is caused by file system reliability or buggy printer drivers. If your case is the latter moving to XML may not help at all.
>
>Amusingly VFP9 SP2 help says "Record your recent actions while using Visual FoxPro and then call Microsoft Support".

I wish there were a way to cause the ISO error on-demand; to test it with XML files. I read much on what is causing the ISO but it does not help since I cannot "catch" it within the application (unless I put every line of code in TRY/CATCH).
I saw the help of that error in VFP help; pathetic.
Thank you.