yess boss.. if all the datatypes are automation compliant, then universl marshalor will do tha mrdhl/unmrshl for us.. rgds... mil10..

Hi db ... Congrats... keep it up and learn more... I can understand ur raising confidence in COM programming day bi day.. keep it up... best wishes ... mil10.

Although I must admit I don't have first-hand experience with anything but Access or MSDE, you could simply create a test function where you execute an insert and catch any exceptions your SELECT @@IDENTITY throws. If there's no exception thrown (and you receive a meaningful result) then @@IDENTITY should work later on as well... Or: Do not rely on a DB supplying such an information in a certain way but create a stored procedure to perform your inserts and let the procedure return the ID of the newly created element. That way you might be more flexible than hard-coding it in your program. Regards, mav

Bob's Hungout has been long dead, and currently I can't even connect. we are here to help each other get through this thing, whatever it is Vonnegut jr. sighist || Agile Programming | doxygen

Ok, i found part of my answer in MSDN .. yaya !! :) The Library article located in Component Development -> Component Object Model (General) -> Technical Articles -> Creating and Registering COM Components with LocalService gave me a big help to get further in my development process but i still fail and one part of the article seems to be my answer, except i'm not too sure how to handle it. Here is the part i'm talking about: Coding a COM component in a service is much like coding a traditional service. In the primary thread, start the service dispatcher thread. Next, expose a COM component through the service and not through the primary thread of the service application. Place the COM-specific code in the service. Finally, create proxies to expose the component's interfaces to any clients. The bold text is what seems to be my answer, but i'm confused as to how to make it. i figured out how to get dlldata.c, _h.h, _i.h, _p.?. So, do i just need to create a dll out of these files ? What kind of registration is required for the Proxy to use my service ? What about UUID's ? Do the proxy component need new UUID's ? I guess being redirected to a good article that talk about proxy/server could help me be less confused. BTW, i'm not using ATL/MFC or whatever .. i edit my IDL file manually. Well, i use MFC but not the COM part of it. Thanx in advance for any hints DarkByte [edit]: Issue was solved by just defining the LocalService key as described in the documentation. My last problem was thinking i was recompiling the Debug version when i actually was recompiling the Release version :doh: