Thanks for the reply! You have given me some things to consider. I need to dig deeper into the code to find out why it takes so long to bring up some of the screens.

>Even 1 or 2 fields * 100K+ records is too much. Sure, once you read the data into memory, things will be faster. Why not give the user a query option to minimize what is brought down to the cleint????
>
>
>>>Hi Larry...
>>>
>>>>In a C/S environment you should be using views to handle your data. If you set the NoDataOnLoad property in the DE for the views, it should speed things up.
>>>
>>>Only on startup. But, if his logic is still set to retrieve all 100+K records, the app will hit the wall again. The key here is to limit the number of records fetched from the server.
>>
>>I have a 'browse' type screen for the users to select a record. I am only bringing down the fields displayed for all the records. It seems like the first time that I run it is slow as it reads the table into memory. From then on it is faster.