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

[pietlinden]

use late binding instead of early binding and then your code should be
less susceptible to problems with installed versions. It may mean you
have to either check for version information in your code or use the
sort of least common denominator when writing your code.

[Zlatko Matic]

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 lata 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

<pi********@hotmail.com> je napisao u poruci interesnoj
grupi:11**********************@g47g2000cwa.googleg roups.com...

use late binding instead of early binding and then your code should be
less susceptible to problems with installed versions. It may mean you
have to either check for version information in your code or use the
sort of least common denominator when writing your code.
<pi********@hotmail.com> je napisao u poruci interesnoj
grupi:11**********************@g47g2000cwa.googleg roups.com... use late binding instead of early binding and then your code should be
less susceptible to problems with installed versions. It may mean you
have to either check for version information in your code or use the
sort of least common denominator when writing your code.

[Zlatko Matic]

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 lata 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

[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 lata 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
"Zlatko Matiæ" <zl***********@sb.t-com.hr> je napisao u poruci interesnoj
grupi:dd**********@ss405.t-com.hr...

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