What Wayne said is almost certainly right-- you don't need lcient server you just need to set up your database and code properly. If you do client server with say SQL Server you'll also have a really slow program if you don't have the right indexes and the right commands. I'm guessing that you have filters on tables that are not rushmore optimized.

Jamie Beerbower


>Wayne,
>
>Thanks so much for your response. It has shed a new light on my assumptions. I will spend today researching those issues.
>
>As an example of what I am talking about for response time, when my client opens up the form for the Master Name table, it takes 30 - 45 seconds for the form to be displayed. There are many tables in the form's dataenvironment and lots of relationships. But I always use indexing and try to ensure continuity between the types of browses and edits that I am doing and the type of indexing that I have things set to. Pressing the EDIT button requires more wait time, though not as much as the initial form display. This particular formset has about 8 tabs (pages).
>
>I guess one of the problems with being self-taught is that I have holes in my knowledge. I come from a mainframe background and but have worked with FoxPro on the side for 11 years. There may be related hardware/software issues in our client/server installation that could be impacting the application. When only one user is on, it runs like a champ! But once several other people start logging in, it bogs down.
>
>Thanks again for your time and input!!!
>
>Fred