Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 229741 - Last Review: July 28, 2003 - Revision: 1.1
BUG: Connection Failure with ADO 2.1 and the Jet 3.51 Provider
This article was previously published under Q229741
If you try to set read, write, or read/write access permissions using the
ADO mode property within your connection string, you receive the following error:
Run-time error: '-2147217887'
"Errors Occurred"
However, if you use the Microsoft Data Link or the Data Environment designer to set these permissions, you get the following error:
Test connection failed because of an error in
initializing provider. 0x80040e21
Remove the
"Share Deny None" mode option from your ADO connection string.
If you are using the Microsoft Data Link or the Data Environment designer, you can deselect the
"Share Deny None" option from the
Advanced tab.
-or-
Use the Jet 4.0 OLE DB Provider instead of the Jet 3.51 OLE DB Provider.
Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.
Steps to Reproduce Behavior
- Right-click on your Desktop, choose New/Microsoft Data Link.
- Fill in the appropriate information to connect to your Access Database via the Microsoft Jet 3.51 OLEDB Provider.
- Go to the Advanced tab. Select read, write, or read/write permission.
- Test your connection. You should get the error.
For more information, please refer to the ADO documentation.
APPLIES TO
- Microsoft ActiveX Data Objects 2.1
- Microsoft ActiveX Data Objects 2.5
- Microsoft OLE DB Provider for Jet 3.51
| kbbug kbdatabase kbdataenv kbdataview kbmdacnosweep kbpending KB229741 |
Retired KB Content DisclaimerThis article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate