Making a copy on the remote server will probably work fine. The only other options I can think of are client/server (which can require quite a bit of additional work), and remote control software (which means you need to dedicate one local PC for every concurrent remote user). As long as they don't need instant access to the data and the other performance is good, your solution should work fine.

>>I have an file-server application that serves 2 separate offices linked through a 256K leased line. The users find the query of one particular table to be unacceptably slow because of the size of the table (about 20M). The speed for the rest of the modules is acceptable.
>>
>>Any suggestion?
>
>I need a quick solution and Client-server may not fit this requirement. I am thinking of freeing this table from the database and keeping another copy of it on the remote server. This table can be overwritten by the updated copy in the server at the end of each day via file transfer. The slow query form will use the local copy of table. All updates will be done to the server copy instead of the local copy.
>
>I have not tried this way before and wonder if there will be any problem. Any idea?