Object library references

[JerryGiese]

I have an access database application that I have developed over the years at work. I am about to change jobs soon and I am working on fixing all the bugs and quirks before I go so other people can continue to use it in the future. An issue I am having comes from upgrading access to a newer version and having to update the library references. For example, when we upgraded to office 2007, I had to go in and uncheck the Microsoft Office 11.0 Object Library and check the newer Microsoft Office 12.0 object library. Is there a way that I can setup this up to automatically choose whichever version of the Microsoft Office object library is currently available on that particular machine?

 

[boblarson]

1. You should not have to check the newer version when upgrading. Access will automatically upgrade it to the correct version if you are going from a lower version (11.0) to a higher version (12.0).

2. If potential users of 11.0 could use it after you have opened it in 12.0 then it will have a reference problem and it would need to be set back to 11.0 for the 11.0 users. This is not a problem if you do not have users from previous versions using it after you have upgraded.

3. To avoid any reference issues it is best to use what is called LATE BINDING where you do NOT set any references and then you declare your objects as objects and then use code like this (for example using Excel in Access):

Dim objXL As Object
 
Set objXL = CreateObject("Excel.Application")

And so on where normally, if you had set references you might have used this:

Dim appXL As Excel.Application
 
Set appXL = New Excel.Application

And so on (the same goes for other lower objects as well).

Does that help?