>>When the main table is queried, a delay of approx. 15 seconds occurs
> >before the information is displayed.
> >
> >This delay occurs every time a record is queried.
>
> What do you mean by "queried"? Do you mean SQL?
>
>No - I don't mean SQL -
>
>By queried I mean this:
>
>The application opens.
>The user clicks on a button (which the programmer has designed)
>called Student Information
>This button open a table displaying four columns and several hundred records.
>The user chooses a particular record in order to see more information about
>that student.
>The user waits and waits and waits and waits (up to 15 seconds) for
>a related table to display more detailed information.

I agree with Bruce. It sounds like the program is not taking full advantage of VFP Rushmore. Or the programmer has done something that prevents rushmore from optimising the query. I work with data on a novell server, that in some cases resides on the other side of the base. I have to ensure through testing that my code is fully optimizable when it is put into place. So I would suggest looking into indexes or testing queries to child records in different fashions noting time on each.