Jan ---- In addition to what Craig posted, try to analyze the way the users will access the data and the program is structured. If you can get away with it, (if your DataSessions are Default in your forms) then consider opening the view upon application load (asynchronously) and keeping it open (refreshing it when required). Another thing to look at is the use of the view properties FetchAsNeeded and MaxRecords. Sometimes you can adjust these settings so that you are dealing with a small "window" of the total data.


>>I want to set up a client server application
>>
>>I am using ODBC and remote views to establish it.
>>Problem: I have to make connection to large databases.
>>
>>If create a remote view of all the records it takes to much time
>>
>>Now i make a remote view of 1 record it working, but
>>i have no skip possibility.
>>
>>Also many of my programs have searche key's that when i'am
>>entering a key the record skips to the matching record.
>>
>>How can help me
>>
>>Kind regards
>>
>>
>>J.J.M. Dorresteijn
>
>Client/Server is a different process. You either work with one record at a time or a set of records. For example, your query would be something like "Get me all the customers in Utah". This would return a record set, and previous/next would work on that set of records.