Thanks in advance to anyone that can help me with this.
We have software in a production environment that uses a DSN-Less connection to access an Access Database. The software was written in VB6 and uses MDAC 2.8
99% of customers have no issues with the software connecting the the database however once in while we encounter a customer that get's the following error:
[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
Except for the DB path the rest of the connection string is hardcoded in the app so there is no difference in the name of the driver used on 99% of the working installations and the 1% that fail. The debug log returned by the customer shows that the following connection string is being used:
Driver={Microsoft Access Driver (*.mdb)};Uid=xxxx;Pwd=xxx;Dbq=C:\Windows\SomeSubDir\ourAccessDB;
We have verfied the following:
1. Our Access DB must be placed under a subdirectory of the main Windows directory. There is special reason for this but it would take too long to explain. However, I have confirmed that the database can be accessed and the user has full permissions on these folders. The can create new files in the same directory, etc.
2. Customer is running Windows XP SP2. Has MDAC 2.8 installed as well as the MS Jet SP8
3. Customer confirms that the entry "Microsoft Access Drive (*.mdb)" shows up in the driver tab of the ODBC panel.
4. I have discovered that I can only reproduce that error on our development systems if I change the connection string to use a driver that doesn't exist (e.g. Driver={Mosoft Access Driver (*.mdb)}
5. Latest users states that this is a "clean" system that is fairly new.
Any ideas would be greatly appreciated.
Take a look at this support article
http://support.microsoft.com/default.aspx/kb/271908
Hope this helps
No comments:
Post a Comment