Problem Connecting to Database

Some more detail, this reference points to:
C:\Program Files\Common Files\System\ado\msado15.dll

On both my computer and the one with the problem, that file is Version 2.81.3012.0

Some more details.

If I type cnPubs. on my machine, I get the list of properties I would expect.

If I type cnPubs. on the problem machine, it displays:
DSO
Session
WrapDSOandSession

I'm still struggling on this. So, does anyone know another way to connect to a SQL database that might be less error prone when using on different machines?

Well, I switched to Microsoft ActiveX Data Objects 2.5 Library, and it works on all machines. If anyone know why that could be though or what to check for, please let me know. I'm still confused because as far as I can tell we all had the exact same dll. We were all on Windows XP SP3 with the same updates, so I'm not sure why 2 out of 4 computers didn't work, which concerns me with rolling out this tool to hundreds.

Apparently I spoke too soon. It does not work on 'all' machines.

It appears that MDAC isn't recommended to install on users machines, so I'm feeling stuck again. If anyone has any suggestions for getting consistency with connecting to a SQL database across machines, please fill me in.

Some more notes to my search:
1. Registering the appropriate dll did not solve the problem (ex. for 2.8 Version below):

Please Login or Register  to view this content.

2. Removing the reference and adding the reference did work though. So, I might start looking at how I could do that through my vba code.

So far, my only solution is to remove and then add the reference on the computer.

There's two major problems with this:
1. I have to set Macro Security to trust the VBA Project Object Model
2. This essentially changes my code, which means that a digital certificate is no longer valid after this is done. Meaning, I'd have to either set macros to always be enabled or force users to enable macros every time they open a file, which users hate to do.

Here's the code to remove and then add the ActiveX Data Objects 2.5 Reference.

Please Login or Register  to view this content.

Another note in my search. I went to spit-out every single property I could in relation to the Reference, and unfortunately they all matched:
BuiltIn = FALSE
Description = Microsoft ActiveX Data Objects 2.5 Library
FullPath = C:\Program Files\Common Files\System\ado\msado25.tlb
GUID = {00000205-0000-0010-8000-00AA006D2EA4}
IsBroken = FALSE
Major = 2
Minor = 5
Name = ADODB
Type = 0

I was hoping to avoid Late Binding due to the performance loss, but it appears to be my best option.

With Late Binding, you remove the reference, and then use generic objects.

Example below:

Please Login or Register  to view this content.

You lose some performance and intellisense (which means you have to replace things like adCmdStoredProc with their equivalent or 4 in this case), but it allows me to distribute the file with less worries about compatibility issues.