Dorris (and Luc),

We used to get that on our network constantly. Finally the network people installed some heavy duty diagnostic tools and discovered (surprise!) that the network load was indeed peaking at those times. It was simply too busy to return the record(s) needed by VFP (5 in this case). Removing some heavy printing (~15,000 pages every 24 hours) to a separate print server solved the problem.

HTH
Barbara

>We see that in a VFP3.0 app on occasion. That particular message is a Novell "Pass-through" error. What we figured out was that after a table update, sometimes the header lock on the memo file did not get cleared. To make matters even more fun, Novell would say that no one had the file locked. To fix it, we look around until we find the person who DOESN'T have that message and have them close out of the app. That usually releases the file and everyone else can work again.
>
>I have had many, MANY discussions with our network people on how to fix it, and the basic answer I get from them is "There is absolutely nothing wrong with the network"
>
>