Hi Bob,

>One of our working hypothesis is that FoxPro is smart about the number of separate workstations working against a file. So if you have one computer running the EXE, no problem. But if you add one other workstation, FoxPro knows that if there is an index on the table, it needs to be brought across the network again after any updates by other clients. So if you have a 10MB CDX on the base table, you might expect a considerable effect on performance.

>Perhaps it is the index information that accounts for all the extra data you see coming across the wire with a second user.
>
>I haven't been able to find any specific information on this aspect of FoxPro and how it handles index information in a multi-user scenario. Have you run across any information about this subject?

No nothing written down ! But what you mention here about getting index information again is that, what I have found, speaking to a bunch of people here in germany.

In my scenario the seconds workstation does really nothing!, so I still do not see a good reason for the more traffic. I will keep you up to date when we find out more.

Scenario: The second workstation just started the application, opening a bunch of objects, tables and views, then we don't touch the second workstation.

Marcus