No definitive answer, but a number of questions come to mind. What kind of network? What speed (10/100)? How many users - total/concurrent? What's the network topology? What are the Server specs - OS (+version), speed, memory, disks (type/raid configuration/etc.), normal CPU load? What are the workstation's specs? Based on these answers and some to questions I'm forgetting to ask, 20 seconds may be bad or even real good!

---

>We have a Foxpro database (designed for us by an experienced programmer) which experiences a 20 second delay in calling a
>data entry screen after a record has been selected.
>
>The main data table holds 56,000+ records. If a record is selected
>from the list, the data entry screen for that table comes up quickly.
>
>If, however, a related table is called (by pressing a button the
>programmer has made) the delay occurs. All the related tables have
>about 10,000 records.
>
>We are using a runtime version of VFP6. The data files are on the
>network. I have watched the programmer perform the same operations
>from within the application (to eliminate the runtime variable) and
>still the delay occurs.
>
>Both tables have key fields through which the records are related.
>
>Any ideas?