Hello.
I performed a quick search and didn't find anything to help, so if there is a previous posting that addresses this, I apologize for not finding it.
My issue is I have built an Access database with numerous VBA code calls and objects. I also reference several libraries, as you might've guessed. Not least of which is the Microsoft ActiveX Data Objects Recodset 2.7 Library - MSADOR15.DLL. However, when I install the databse on another machine, this library is unfound and error ocurs upon first call to a function in this library.
So, I can copy the library file to the new machine and then link the reference to the copied library file to make everything work, but I certainly don't want to have to walk people through having to do that on every machine to which I distribute the database.
I've checked a couple articles, including "Access Reference Problems" (http://members.rogers.com/douglas.j.steele/AccessReferenceErrors.html) and several of the articles referred to within, but cannot find anything concrete. The closest solution is that one of them says that the library file search path includes the folder in which the application resides, which in this case is Access. Unfortunately, it seems as though this could be, and likely is, operating system dependent, otherwise I'd simply copy the library to where I suspect msaccess.exe resides.
Do any of you have another reasonable solution? Or, am I simply missing something obvious (this has certainly happened before!)?
Any assistance you can provide would be most helpful.
Your humble student,
Tom
I performed a quick search and didn't find anything to help, so if there is a previous posting that addresses this, I apologize for not finding it.
My issue is I have built an Access database with numerous VBA code calls and objects. I also reference several libraries, as you might've guessed. Not least of which is the Microsoft ActiveX Data Objects Recodset 2.7 Library - MSADOR15.DLL. However, when I install the databse on another machine, this library is unfound and error ocurs upon first call to a function in this library.
So, I can copy the library file to the new machine and then link the reference to the copied library file to make everything work, but I certainly don't want to have to walk people through having to do that on every machine to which I distribute the database.
I've checked a couple articles, including "Access Reference Problems" (http://members.rogers.com/douglas.j.steele/AccessReferenceErrors.html) and several of the articles referred to within, but cannot find anything concrete. The closest solution is that one of them says that the library file search path includes the folder in which the application resides, which in this case is Access. Unfortunately, it seems as though this could be, and likely is, operating system dependent, otherwise I'd simply copy the library to where I suspect msaccess.exe resides.
Do any of you have another reasonable solution? Or, am I simply missing something obvious (this has certainly happened before!)?
Any assistance you can provide would be most helpful.
Your humble student,
Tom