> >
> > No shared files such as databases should be using opportunistic locking.
> >
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;Q129202
> >
> > Make a point of testing with at least two workstations as the norm.
>
>
> What exactly did you mean with this point?
>
> I suppose the registry value of "EnableOplocks"
> on the server's
> \HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet
> \Services\LanmanServer\Parameters
>
>
> should be set to 0.
>
> I tried to do that (with 0 and 1), but no difference in performances.
> Actually, it is even worse with setting to 0.

That is not a logical statement. "Even worse" is not "no difference".

>By default there was no registry key and I added it. If it was set to 1, >performances were same as there was no key, but setting to 0 the access was slow >even with first user.

I'm sorry to tell you, but you will have to accept the slower performance as the standard. You must set it to 0, which will make the behavior consistent for *ALL* users. That is the important thing. There is no way to make it that fast for all users. It will also reduce corruption. Rushmore and indexes will make the building of the cursor faster as the number of records will be small - as they should be.

> It is interesting - when I connect to the server directly with 2 remote desktops at the same time, it isn't problem as it is with 2 users from real network workstations. So there must be something that could improve this multi-user access.

Via remote desktop, there is really only one user, IMO, the server.

Mike Yearwood
Microsoft MVP Visual FoxPro 2008



We have enough youth. We need a fountain of smart!
There may be many ways to skin a cat, but there are very few right ways to do it.