Access Late Binding Question

[Guest]

I am using Access to keep some data that is being used by a Word Application.

Access populates a drop-down list and I have developed it in Office 2003 but
we have users on 2002 and 2000 so I need to use late binding. I had done
early binding in the initial development and included the Microsoft DAO 3.6
reference and everything operated great.. But I am unable to locate the
structure for "Access.Application" heirarchy of objects to convert the code
for late binding. For instance, when I try to take the Access object and use
it to address an existing database it always Opens the database and if I have
visible=false it opens it in visible format THEN makes it invisible.
Alternatively, I tried to GetObject and again it opens it in visible format
THEN makes it not visible. Similarly, when I try to create recordsets, etc I
get the 429 error and I am sure that I have just missed an intermediate step.
Is there a good source for this?

I appreciate any pointers you might have. I posted this on the Office VBA
group yesterday and someone suggested that I write the code for the oldest
version of Office and it should work on the current versions. While I am not
writing anything very sophisticated the code still insists that it be
re-compiled between the 2003 and 2002 versions -- I am referencing Microsoft
DAO 3.6 and this is either located in a different place or is registered
differently -- because when it opens on an Office XP system the reference is
not checked and has to be checked and the code saved under that system and
vis-a-versa so I am sure that late binding if done right should resolve these
problems.

Thanks for your time and consideration.

 

[Alex Dybenko]

Paul,
normally to convert early binding to late - is to dim all objects as Object
and use createobject() to initiate objects like Access.Application
as for DAO - you can also use late bindings, but for all 3 access versions
you using - there is the same DAO version, so here you can use early
bindings
And one more thing - make sure that DAO360.dll correctly registered,
look at http://support.microsoft.com/default.aspx?scid=kb;EN-US;319841