>I just looked up the PROGID in the registry as well so you don't have to use the CLSID to do this (as in the previous example)... here's the code:
>
>

oGAEB = CREATEOBJECT("GAEB_XML_TOOLBOX.V2.00")

>
>...so either that or the following should work for you...
>
>

oGAEB2 = CREATEOBJECTEX("{20000999-75F1-11D3-A2D7-00500448294A}","")

>
>
>In case you're wondering, with that other COM Server that was with the files you sent... it's either:
>
>

oGAEB = CREATEOBJECT("GAEB_TOOLBOX.V2.00")

>
>or
>
>

oGAEB2 = CREATEOBJECTEX("{20000999-65F1-11D3-A2D7-00500448294A}","")

>
>
>Here's where the information is located in your registry if you're curious:
>

For GxmlTbv2.exe
>[HKEY_CLASSES_ROOT\CLSID\{20001001-75F1-11D3-A2D7-00500448294A}\ProgID]
>[HKEY_CLASSES_ROOT\GAEB_XML_TOOLBOX.V2.00\CLSID]
>
>For GaebTbv2.exe
>[HKEY_CLASSES_ROOT\CLSID\{20001001-65F1-11D3-A2D7-00500448294A}\ProgID]
>[HKEY_CLASSES_ROOT\GAEB_TOOLBOX.V2.00\CLSID]

Thanks Craig,

it really works, thanks. I've tried with the CLSIDs, either, but I tried the whole time to put the name of the class after the name (or the CLSID) of the library. That must be some misunderstanding on my part and I still do not understand it. It seems that the COM-Server itself exports all the Functions regardless of the classes in which they are packed inside of it. And the classes themselves cannot (and must not) be instantiated. Can it be? Well, obviously it is so...

Thanks once again