>>We have never experienced this problem on a IntraNetWare 4.11 network
>>with Client 32 2.1 or 2.2, but, crucially, with VFP5.
>>Could this be another VFP6 blunder ?
>
>We are currently on 4.10, but moving to 4.11 on Monday. I will report back on the results.

Just to make you feel better, I used to get this on an NT network and VFP5. We played with rights/permissions and fixed it without knowing exactly what was the cure. tried to recreate and couldn't. I hate those kind fo problems.