>have you tried closing the underlying table after each open/update/requery on a regular or framework basis ?
>
>Reason for asking:
>In some clientOS / serverOS constellations vfp is slowed down considerably if a table is opened concurrently by more than 1 machine (different processes on the same machine are still the same speed - which lets me guess to a more OS based problem).
>
>In theory with not too often/long used tables the practice of closing the tables could help here - but I haven't tried that as basis for continuos use (and it would mean for instance that common lookup tables for combos and should be eliminated <g>). Any experience to draw on ?
>

I haven't tried closing the source tables in a real working environment. I've only done it on an experimental basis to learn what was going on. I would look into what's causing the network to slow down, rather than trying to close the tables. It sounds like that's more of a problem. If you try the technique of closing the tables, you might find yourself fighting with how VFP wants to work.