We are currently working with Axapta 2.5 running on Windows 2000 Server connecting to the Enterprise edition of SQL Server running on Windows 2000 Adved. Our problem is in regards to the Axpata client COM connector. We are looking to maximize our scalability and one of our key problems is with the COM client. Currently we have the client installed on the SQL system, registered as COM+, and connecting to the AOS server. We use the sp_oacreate set of stored procedures to call the component and to run our code. What we now need to do is somehow be able to get away from having the axpata client and COM+ client installed on our sql server. My question is, has anyone had any luck calling the COM+ component from a different machine? Because it is COM+, I have tried the method for exporting it as a COM+ application proxy but when I go to install it on the client, it fails. Is there a special way to register the client to get it to work in this fashion? Thank you in advance for you help Chad Ewing