missing references

[Zlatko Matiæ]

Hello.

I prepared a .mde file using Access 2003.
When I tried to use it on a computer with Access 2002 installed, it didn't
work, because some references were missing (lower versions). Therefore I had
to manually adjust references to lower versions, first in .mdb and then
create new .mde file on the client computer. Although it solved the problem
in this case, it is obviously not the best solution, because I can't be
phisically present on every client...
My question is the following: How could I be sure that client computer has
all neccessary references, despite which Access version is installed. Is
there any downloadable file with most recent VBA that could be incorporated
in my installation along with .mde file?
By the way, I bought a program called MDE2000 (RV Software) that can produce
Access 2000 compatible .mde file by using Access 2003. It is great thing,
but useless if client computer with MS Office 2000 doesn't have all
references as my Access 2003....
How to solve this ?
Thanks,

Zlatko

 

[Douglas J Steele]

If you're talking lower references of specific applications, the answer is
to use late binding, so that you don't need to set references at all.

Tony Toews has an introduction to the topic at
http://www.granite.ab.ca/access/latebinding.htm

 

[Zlatko Matiæ]

Hello,

I think I still don't understand late binding...
Could you please give some example of late binding in Access (examples were
for Excell)?
Thanks.

 

[Douglas J Steele]

Actually, the examples given are for how to automate Excel from Access using
Late Binding.

http://www.mvps.org/access/modules/mdl0006.htm at "The Access Web" is a more
complete example of automating Excel from Access using Late Binding.

 

[Zlatko Matiæ]

I was reading about late binding in meantime, but I'm not completely sure
what is to be done in order to adjust code to late binding...
For example, I'm not sure if this is correct:

early binding:

Dim ws As DAO.Workspace
Dim db As DAO.Database
Dim qdf As DAO.QueryDef
Dim rs As DAO.Recordset


late binding:
Dim ws as Object
Set ws =CreateObject("DAO.Workspace")
Dim ws as Object
Set db =CreateObject("DAO.Database")
Dim qdf as Object
Set qdf =CreateObject("DAO.QueryDef")
Dim rs as Object
Set rs =CreateObject("DAO.Recordset")

VBA help says that class argument inside Create object function has to be in
appname.objecttype format. Does it means that DAO should be preceded by
"Access", so the previous code should be like this:

Dim ws as Object
Set ws =CreateObject("Access.DAO.Workspace")
Dim ws as Object
Set db =CreateObject("Access.DAO.Database")
Dim qdf as Object
Set qdf =CreateObject("Access.DAO.QueryDef")
Dim rs as Object
Set rs =CreateObject("Access.DAO.Recordset")
?
What exactly I need to change in my code in order to support "late binding"
?
All examples given in VBA help and internet are concerning late binding in
case of calling other Office aplication from Access, but I couldn't find
examples of late binding inside Access itself...so I'm little bit confused.
Is there any Add-in or program, that can change early binding declarations
to late binding declarations through all modules automaticcally ?


Zlatko

 

[Douglas J Steele]

There was no need to start another thread (which I've already answered).

As I said there, I don't believe you can remove the reference to DAO and use
late binding on it.