John,

Thanks so much for your reply to my problem.

From working with this client, there is not a lot of other network talk going on. It is primarily used just for a few client/server applications
for that office and a small amount of Internet transmissions.

> 1) locates or views against big tables using unindexed expressions;
This is one of the major things that I am zeroing in on now. I always access the actual tables, not views, in my application. However,
I always use unique indexes and optimizable expressions. Occassionally, I use SET FILTER TO, although I really don't care for the
performance of this very much. My techniques have worked ok for me in the past, but the environments and needs have changed
and it looks like I have some gaps in my client/server knowledge that are coming to light with this latest application.

I have tried making many of my tables read only except for the ones that absolutely needed update capability, I had read that this
could save time.

> 2) table file header locks (caused by replace for / append blank which "lock" the whole table; use update / insert instead to get
> record-level locking, or move to views)
I've always been careful of this one and I'm sure that I am not hitting against this. The sluggishness of the system is present even if
everyone is only browsing the tables.

I am spending this evening and the upcoming weekend researching about views and how to use them. Thanks so much for your time
in answering my question. I'll let you know how I come out.

Fred