>Hi Vlad,
>
>Do you mean to say that in this approach, if the server is powerful it will accelerate the speed of processing compared to a client registered dll?

Yes, it is possible when at the server side there are a lot of code running.

>But if a number of users lets say 20 consecutive users accessing the dll on the server at the same time it will slow up the processing?
>
>I have atleast 30 users using the system.
>What would you suggest?
>

The slow down is in the communication, as I said. Assume during saving of some data for one form you require to update 30+ tables. COM object has a method to update data on server for one table at time. Assume each table saving requires 6 requests to COM object methods and properties. You will require to make 180+ requests to COM object. Multiply this number to the time required for communication between client and COM object on server through DCOM and you will get quite a big slow down. Now multiply this number to number of users comnnected simultaneously. In case all users do requests to COM object at the same time, you will get significant delays. It is good idea to build COM object in such case such way that it is required only to call COM object 6 times to update all tables at once.

As you see, good performance require more complexity and coding, sometimes it is not avoidable. Just see if this is a case in your application.

There are also other cases of slow down or breaks in the system, but they're more rare and related mostly to DCOM connection through Internet.

>Thanks again...
>Mike