Problem with References

[Scott Burke]

There are many reasons why computer "A" has a reference and computer
"B","C",ext... does not. I really dont wont to go into details why.

With that said.

Problem: I write the software on computer "A". Computer "A" has the
reference "Microsoft ADO Ext. 2.8". However computers "B","C","D" only have
reference "Microsoft ADO Ext. 2.7". However computer "A" 0nly has "Microsft
ADO Ext. 2.8".

Right now I am looking for Ideals on how to fix this programmicly (sp?)
Updating the computer OS and Office is NOT in the budget this year.

I am thinking that the solution will be something like this:
1) Write two vba functions. One for computer "A" the other for computer
"B","C","D"
2) Make a Macro "Computer A" that runs "FUNCTION A" ....ect...ect...ect..
That way I could put the program on the others computers and use the Macro
to change all the references that need it.

Keep this in mind. I simplfied my problem. Each computer has different
references.
Your ideals?

 

[Rick Brandt]

There are many reasons why computer "A" has a reference and computer
"B","C",ext... does not. I really dont wont to go into details why.

With that said.

Problem: I write the software on computer "A". Computer "A" has the
reference "Microsoft ADO Ext. 2.8". However computers "B","C","D"
only have reference "Microsoft ADO Ext. 2.7". However computer "A"
0nly has "Microsft ADO Ext. 2.8".

Right now I am looking for Ideals on how to fix this programmicly
(sp?) Updating the computer OS and Office is NOT in the budget this
year.

I am thinking that the solution will be something like this:
1) Write two vba functions. One for computer "A" the other for
computer "B","C","D"
2) Make a Macro "Computer A" that runs "FUNCTION A"
....ect...ect...ect.. That way I could put the program on the others
computers and use the Macro to change all the references that need it.

Keep this in mind. I simplfied my problem. Each computer has
different references.
Your ideals?

Install what is necessary so that all computers have the same libraries or
switch to late binding so you can eliminate the reference.

 

[Scott Burke]

HI Rick. How do you install "Microsft ADO Ext. 2.8" on a computer that does
not have it? Can you install just "Microsft ADO Ext. 2.8" or do you have to
install a version of access to get it?

Scott Burke

 

[David Harry]

I had the same issue:

I decided on Late Binding instead of Early Binding.

Early Binding requires you to set the References (Microsoft ADO Ext. 2.7 for
DDL and Security) before you use the object

Dim cat As ADOX.Catalog
Set cat = New ADOX.Catalog

With Late Binding, you can uncheck the reference (2.7 or 2.8, above) and set
it when the program runs.

Dim cat as Object
Set cat = CreateObject("ADOX.Catalog")

So the reference on the other users computer (computer B or C, etc.) will be
set when it is utilized, not when it is declared.

This will have some consequences, particularly a bit slower performance,
because of compiliation during the application, not before.

Hope this helps!