Hi!

Of course, there will be a slow down, because all will work through LAN. This is not so sognificant, unless you're calling COM object multiple times (50 or more)/per user request. It is good idea to call COM object in such case in few requests only. Each request to COM objec for property value or method call require communication between local and remote computers and that takes additional time. Sometimes when server machine is much more powerful than client's, this speeds up work - COM component on the server does job more quickly, and as a result respons more quickly,making an illusion of improved performance. The illusion quickly becomes off when you will try the system with 10 or even 100 users - the communication time becomes quite significant.

All this is more LAN speed, reliability and server reliability/power problem in such case.


>Thanks for the info Vlad. Currently, I use the CreateObject() function to create an instance of the function / method within the Dll. If I will use CreateObjectex() function, will there be a great significance of slowness compared to the CreateObject() function? Will a single Dll being accessed by many clients work just fine as compared to registering the same dll on each workstation?