>>>>I have no problem on the development machine but a user is complaining that they get an "Invalid seek offset" message when trying to exit the application. This is a VFP style message, not my error routine, with no further info. The only way to get by this message is to reboot/End Task. Anyone else see this or know what it means?
>>>>
>>>>Thanks
>>>>Elyse
>>>
>>>Try ReIndexing/Recreating your indices. Generally when I see that error, it's because one of the tags has gotten bashed
>>
>>If they have any Symantec software app's (Norton Anti-virus, PcAnyWhere), remove them and try it again. I experienced a similar problem and tracked it down to PcAnyWhere being loaded (does not need to be running) on the PC. If the problem goes away contact Symantec about it. It took a while but they finaly fixed it for me. My Case Id number was 400 749 4388, it may come in handy.
>
>Hi Dan!
>
>We have had the same problem on a Windows 95 network, where the server had PCanywhere32 installed (but not running).
>
>VFP 5.0 kept crashing out on this error.
>
>So great to see the above tip - it would have been tricky to track this down otherwise.
>
>Microsoft has logged this on their Knowledgebase for VFP article no Q162412.
>
> As always, reading this plus linking into Symantecs site for the patch only confuses the issue.
>
>Do we only copy the patched files as recommended by Symantec?
>
>Or do we also patch the registry as recommended by Microsoft?
>
>This patch refers to the removal of the value reference for the string 'Symevnt.386' (I think that this
>MS talk for deleting this line from the registry).
>
> If so, there are multiple occurances of this string.
>
> Do we delete them all, or only in the section noted by MS in its article under 'Cause'?
>
>Hope you (or anyone else) can help.......


I was not aware there was anything in the knowlege base about it. I started having the problem with VFP3.0. I began to notice patterns and wrote a test application to amplify the problem. I sent this application to Symantec with instructions on how to duplicate it and about six months later, after many phone calls to let them know I had not forgotten about it, I recieved a patch.

To answer your question I will try to remember back. 'Symevnt.386' is a driver that somehow insulates your files from access by any other software. They use this for their virus software. From what I understand this driver is used by a lot of their other software including pcAnyWhere. It is installed to be active all of the time even when you are not installing it with the virus software. I just read the knowledge base article and I don't know. The regestry edit is probobly a means to disable it because I don't think it has to be active(just present) with pcAnyWhere. All I did was install the patch they sent me. I doubt that it was a patch that they released to the world. I have since upgraded to the latest patch and have not seen any problems. I think I would work in steps starting with the patch. The registry thing scares me. Symantec had me disable it somehow(I don't remember, something in a windows ini file.) and it improved disk access considerably. The registry may be another way of doing the same thing.