>>>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)?
>>
>>It has been a long time since I resolved that. The illigal offset in my cases Always had to do with Network connections that were dropped (even briefly). Since we've upgraded to SQL server and hold all the meta data locally or embedded in the executable, I have not seen it since.
>>
>>Walter,
>
>My app is also using SQL Server and the meta data are in the executable. But still, once in a while, I get messages (from customers) of that dreaded ISO error. This is why I am thinking of changing meta to XML. I presume that your meta data is DBF, right?

Yes. DBF. I've never encountered problems with that. Where is your executable run from? From the network or from the workstation? If from the network the problem could just be that the network connection is lost. VFP reads the executable when running code. If the networkconnection drops, the executable cannot be read anymore and an Illegal Seek offset will be thrown.

Best is making sure using a launcher and make sure it is run locally from the workstation.

I do not think that a change to XML would change anything. The cause is unrelated to the DBFs if they are embedded in the executable.

Walter,