Hi David,

It is a COM DLL ( instantiated with createobject() ) built using the ATL Wizard. I believe I want this type object since the ultimate intention is to use it in a web page instantiated using createobject() in VBScript.

I chose the ATL Wizard because presumably you can build a lightweight item with it ( i.e. lighter than using the MFC with it's overhead ). Honestly, in relation to COM DLL vs. API style DLL, I don't know what switches have to be thrown to determine which it will be. What determines this attribute?

Since you say that the COM DLL handles everything with VARIANT type parameters, it generates a couple of questions. How would these parameters be declared on the C++ end in this case?

Since I want to make API calls in the DLL to return system data, am I approaching this the wrong way, and if so, what should I do different?

Thanks,
Bill

>
>Are you building a COM DLL (using createobject) or an API style DLL (using declare dll)? COM handles everything with VARIANT type parameters. API allows direct function calls to the VC++ methods using specific types of parameters. If you are doing COM the article on using VFP COM from VC++ on www.west-wind.com would be a good thing to read.
>
>>I have also posted a more thorough statement of my problem in the thread "ATL COM DLL parameter passing", Thread #357041. The main difficulty seems to be in the parameter types allowed for passing across COM interfaces. This is an area I don't understand well. My first message in the thread gives the details. I am missing something in this regard.