Relationships Between Properties & Type Libraries?

[Dave]

Is there documentation for the linkage between object/properties/
methods and their respective type libraries (references required to be
set in the VBE)? Usually, in what you find on the 'net, somebody
mentions the reference required to do what one has searched for. When
you can't find exactly what you're trying to do, such documentation
would help. So far, I've looked in Access and VBE Help, the VBE Object
Browser (which, BTW, apparently only lists objects you've set
references to) and the 'net, all to no avail. Sometimes, "See Also" in
Help gives a clue in that you might see "DAO" in the short list of
topics. Since you're going to ask "What are you trying to do?" Here it
is:

- validate or set/repair missing references from a table list of
names, guid's and paths. Seems to me there's at least two advantages
to using a table. 1) when you import everything into a new database
(for any one of many reasons) the table of references will be there
and should be repaired upon startup. 2) you could even make this table
application specific by including the application name property. I
have not found any posting where this has been done. The closest was
where the list was contained as string values in the code itself.
Before you suggest looping through a DAO recordset based on the table,
note that DAO is not an automatically set reference, thus the code
will fail. I've dismissed DLOOKUP (even if it would work) as an un-
elegant solution. If you have a solution, that would be great but a
link to a document specifying the reference required for an object or
property would be great too!
Thanks.

 

[Douglas J. Steele]

What version of Access are you using? With the exception of Access 2000 and
2002, DAO is set by default.

It's not really clear to me what problem it is you're trying to solve. See
whether what MichKa has at http://www.trigeminal.com/usenet/usenet026.asp
addresses your concerns though.

 

[Dave]

What version of Access are you using? With the exception of Access 2000 and
2002, DAO is set by default.

It's not really clear to me what problem it is you're trying to solve. See
whether what MichKa has athttp://www.trigeminal.com/usenet/usenet026.asp
addresses your concerns though.

Sorry, I should have said I was using 2002. I was trying to loop
through a table of references complete with guid's and the network
paths to the type libraries or dlls as the case may be; if missing,
add the reference; if broken, repair it. Since posting, I've found
that certain properties and methods are there by default even in 2002,
as long as you don't specify DAO and code it correctly. I have manage
to do the add part so far with nothing but the 2002 default
references. I did not know how to code it without using the syntax for
DAO or ADODB. At this point, I'm not sure if I can invoke the
references dialog if the path can't be resolved. If not, no big deal,
I'll just report which one can't be added/repaired.

I guess my base question though is, other than searching access forums
and the like to find out how to do something (thus learn the
associated required references) where do you go to learn what
references are associated with what. For example, such a knowledge
reference would say, in order to use SMTP mail, look at CDONTS and
CDO, and here's a list of methods and properties provided so you can
figure out which one to use.