Re: multiple idl files with a single type library

From:

"Igor Tandetnik" <itandetnik@mvps.org>

Newsgroups:

microsoft.public.vc.atl

Date:

Tue, 9 Oct 2007 18:43:56 -0400

Message-ID:

<uFMgrcsCIHA.5044@TK2MSFTNGP03.phx.gbl>

safpaul@gmail.com wrote:

I would like to use two idl files with one library. I have the
following files:

enums.idl:
//////////////////////////////////////////////
[ uuid("c28c1dbc-a47a-41df-1237-7a353f029e34"), helpstring("enYMD") ]
typedef enum enYMD
{
enYMD_YEAR,
enYMD_MONTH,
enYMD_DAY
} enYMD;
//////////////////////////////////////////////

main.idl:
/////////////////////////////////////////////
import "wtypes.idl";

[
uuid(6F818C55-E6AD-488b-9EB6-511C0C123612),
version(1.0),
helpstring("CIFG Version of S&P Analytics")
]
library SandPlibComServer
{
import "enums.idl";
importlib("stdole32.tlb");
importlib("stdole.tlb");

}
///////////////////////////////////////////////////////////////

when I compile, I have no problems, but when I access the dll from
Excel VBA, the enum type is not available.

You need to mention the enum from inside library block - like this:

enum enYMD;

Personally, I'd also drop the typedef, you don't need it:

enums.idl:
//////////////////////////////////////////////
[ uuid("c28c1dbc-a47a-41df-1237-7a353f029e34"), helpstring("enYMD") ]
enum enYMD
{
    enYMD_YEAR,
    enYMD_MONTH,
    enYMD_DAY
};

--
With best wishes,
    Igor Tandetnik

With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea. It is hard to be sure where they are going to
land, and it could be dangerous sitting under them as they fly
overhead. -- RFC 1925