I hope this helps anyone else that might have this same issue arise with them. I decide not to go this route unless I had to because I already kill the Office applications on one machine by copying my maso15.dll file to their machine. I read some where in the MS knowledge base to do this in a test environment because it may cause some problems. I was looking in to the redistributable installer for the MDAC 2.8 release and was going to run it on all our computers 15-20. I figured this must be why it showed that the reference library was missing but when I went to the path of where it was suppose to be the file was there. I download the file and discovered that there where different version of the maso15.dll file. In the Microsoft knowledge base you can download a program to check which version of Microsoft Data Access Components (MDAC) that is installed on a system. Since this will only be used in my group I can easily have one co-worker add the reference library on the remote computers. You might not want the user to have access to your VBA code.
Of course this method will not work for everyone. The ADO 2.8 SDK consists of the following components: Microsoft ActiveX Data Objects (ADO) enable client applications to access and manipulate data from a.
In fact one user had Microsoft ActiveX Data Objects 2.5 and this worked fine. By not checking the reference library to Microsoft ActiveX Data Objects 2.8 in my PowerPoint file (Tools>Reference) and letting the user install it you did not run in to any problems will different version of the msao15.dll file.
0 kommentar(er)
