"ron paii" <none (AT) nospam (DOT) com> wrote in
news:j4tef4$kog$1 (AT) dont-email (DOT) me:

If it's a COM component, it shouldn't matter.

--
David W. Fenton http://www.dfenton.com/
contact via website only http://www.dfenton.com/DFA/

ron paii wrote:
It's a COM object or else you wouldn't be able to use it in VBA. What you
need to find out is the name of the COM library containing that object.
Let's look at your code:

So what this line of code does is instantiates a new EdmVault5 object and
points the m_Vault variable at it. Notice that you did not have to qualify
the EdmVault5 object name with the name of the COM library that contains the
object.

The reason this line of code works is that you set a reference to the
library containing this object in Tools>References. Because you did that,
you did not have to use CreateObject to instantiate it. In addition, you
were also relieved of the requirement to qualify the object name with its
library name.

If you try to create a recordset object using

Set rs=New Recordset

when you have both ADO and DAO references, you have to qualify the object
name in order not to get the "default" object, which depends on the order
the references appear in your References list. I.E., if ActiveX Data Objects
appears first, you will get an ADODB recordset. If DAO is first, you will
get a DAO recordset. In order to control which one you get, you need to
qualify the object with the name of the library.

To guarantee you get a DAO recordset, you need to use:
Set rs=New DAO.Recordset
If you want an ADO recordset you need to use
Set rs=New ADODB.Recordst

If you want to use late binding to get an ADO recordset (without setting a
reference), you have to use CreateObject (using New requires a Reference)
and you have to use the fully qualified object name when calling
CreateObject:
Set rs=CreateObject("ADODB.Recordset")

Are things becoming clearer yet? Hopefully you are beginning to realize the
need to discover the name of the library containing that EdmVault5 object. I
think the easiest way to do that is to use the Object Browser in the VBA
IDE. When you open the Object Browser (press F2 while a code window is
open), you should see a dropdown that will contain the names of all the
libraries for which you have set References (usually Access, DAO, VBA and
stdole will be listed, along with any other libraries you have Referenced).
It should be fairly simple to look at that list and figure out which one is
the EDM library. If not, type EdmVault5 into the search box and click the
search button. The search results include a column for the name of the
library containing the class (object).

Alternatively, you can search your machine's registry to discover the name
of the library, but you should not have to if you've added a Reference to
the library.

Anyways, once you have the name of the library, you should be able to
instantiate EdmVault5 using:
set m_Vault=CreateObject("<libraryname>.EdmVault5")

"Bob Barrows" <reb01501 (AT) NOyahooSPAM (DOT) com> wrote

After adding a reference to "PDMWorks Enterprise 2011 Type Library
The library name listed in Object Browser is EDMLIB

Replacing
Set m_Vault = New EdmVault5
with
Set m_Vault = CreateObject("EdmLib.EdmVault5")
results in error number 429, ActiveX component can't create object

I am thinking that because it is implemented as a file explorer add-on, I
need to automate explorer?

ron paii wrote:
In my experience, if you can use New to instantiate an object, you should be
able to use CreateObject. This is puzzling.

What happens if you try
Set m_Vault = New EdmLib.EdmVault5
? If that also fails, then that cannot be the library's name.

I suggest you try to find a forum/group devoted to that tool and ask there.

"Bob Barrows" <reb01501 (AT) NOyahooSPAM (DOT) com> wrote


Set m_Vault = New EdmLib.EdmVault5
worked.

All the support for this API is in .NET, I had to translate it to
Access/VBA.

ron paii wrote:
The only explanation I can come up with for this is that EdmLib depends on
another library. Adding a Reference makes that transparent so you don't need
to fully qualify it using New. Without the Reference, you need to explicitly
qualify every part of the path that gets you to EdmVault5. I would use
Object Explorer to dig into it. Perhaps SysInternals Process Explorer can
help.

"Bob Barrows" <reb01501 (AT) NOyahooSPAM (DOT) com> wrote


If the 1st reference of EPDM application is though explorer.exe, process
explorer creates EdmServer.exe under explorer.exe on the same level as
Access. If the 1st reference to EPDM is from Access it is under
MSAccess.exe; If I close Access EDMServer.exe is restarted on the same level
as explorer.exe. In all cases it creates 5 copies of the same dll
"EdmInterface.dll!DllUnregisterServer+0xc4188" .

"ron paii" <none (AT) nospam (DOT) com> wrote in
news:j57ogm$mb4$1 (AT) dont-email (DOT) me:

I don't think that's the right name for the object.

I would search for the DLL/OLB file in the registry and see if the
name is found there. That's how I've always done this.

--
David W. Fenton http://www.dfenton.com/
contact via website only http://www.dfenton.com/DFA/