>>I can only say that some of the methods should be reviewed and time testing should be done with a variety of number of users accessing the table at the same time. In other words, sometimes a method that proves to be the fastest when you are accessing the table as the single user will not be the fastest method when there are many users.
>>
>>I would also check each operation to see how fast (slow?) it is when done from a remote machine and how it does from the application run on the file server. If the file server can do some operations a LOT faster, I would explore the use of DCOM to get these operations done on the file server.
>>
>>I guess you might want to look at SQL Server too if this continues to be a problem.
>>
>>Joe
>>
>>
>
>Hi Joe,
>
>All time testing has been done, it works ok normally. DCOM and SQL Server won't be quick enough - they want answers NOW. I've given them the option of having the inserts queued through an interim table. I think that's the quickest option.


Good luck.

Joe