>Invalid Seek Offset
>There isn't much information in the help on this one. The entire contents of the help is "Record your recent actions while using Visual FoxPro and then call Microsoft Support." --- great!
>However, I found that if I opened a network table in foxpro and then disconnected from the network, and then returned to foxpro the error would occur.
>What do you know about Invalid Seek Offset? Is it soley a network issue? Are there any other known causes for it?

The old cause was corrupt indexes, but that's not usually true any longer, I think. Still, it's the first thing to look at.

I still have not solved ISOs, as I call them, that occur only on test NT WS machines here. We cannot move to NT unless the problem is solved, and I have about given up solving it - I know it is a configuration problem, but I cannot pinpoint it. They are caused by "network interrupts" of some sort, I believe, but no one has been able to help, including MS. ISOs cannot be reproduced with Win95 or 98, and they occur in both vfp5 & 6, but only on NT.

One thing you can test is to put the entire app & DB on a hard drive, see if you can reproduce the ISOs with/without network connection. I can do that here, rather amazingly, even with no connection to the vfp server open - so I know the problem unrelated to the vfp server with me.

As to losing multi-users, we solved that here easily by disabling McAfee Server service. It wasn't just vfp that was losing users, other apps had the same problem on a number of busy NT servers. Disappeared with McAfee removed from servers.