Well this is not really an answer but a question. Why are you in need of wrapping this dll? Yes, I have done this. No, I didn't enjoy it. My preference is to rescope the entire project and hey just do away with the old dll if possible. If its not possible then I create a COM object that calls the other dll. Basically all calls on the old dll would be new methods on the COM object. I think you may be pushing the boundaries on the structure sizes but I am not entirely sure. If you have no requirements to use IDispatch then I would create a custom interface and just pass in the structures or pointers of structures as the case may be. You will need to look at each structure on a case by case basis to see if it is okay. You can pass the char* if you know the size. This is a big topic. I feel an article coming on. Mike "Cop" Pulice mike@puliceworx.com

Hello All, I work in the Wireless Industry and have most of my experience in developing Engineering tools and Test Applications. In the process I have discovered that source and config management for all of these different test apps is a pain in the rear. So, what I have come up with is this architecture. One GUI Application (Client). Multiple Test Servers (GUIless Applications). It is basically a Generic GUI that connects to multiple test servers. The test servers utilize COM categories and derive from a common interface that the Generic GUI can use. Does anyone have the desire to read this article or download the code? Thanks, Mike "Cop" Pulice mike@puliceworx.com

Anyone interested in a hierarchy model for ports? Something like CPort - CSerial - CUSB Mike "Cop" Pulice mike@puliceworx.com