471,338 Members | 1,491 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 471,338 software developers and data experts.

URGENT | VB.Net | Access DB connectivity

Hey,

I'm facing a very strange problem.
We have a windows application being maintained in CVS (not VSS!!!! and i
hate it! but nevertheless....)
Within this application, we are connecting to an MS Access database, using
the connection string:
PROVIDER=Microsoft.Jet.OLEDB.4.0;Data Source=" & strDBPath & ";Password=" &
strDBPassword
where strDBPath and strDBPassword are being picked up from the config file.
Now the project builds alright on all the machines, save for one, where
we're getting the following error:
"No Error Information Available : VB.NET DB_SEC_E_AUTH_FAILED(0x80040E4D)"
This is pretty strange, as due to this error, no form is opening up in the
design mode.

Has anyone faced a similar problem???
Tried searching on Google, but there again, it generally comes in when ppl
have used very large excessive connection strings, and merely changing the
connection string to the version that I am using has rectified the problem in
almmost all cases that i browsed through.
Any pointers gladly appreciated

Cheers!
Nick
Aug 10 '05 #1
2 2998
On Wed, 10 Aug 2005 00:56:04 -0700, "Nick" <Ni**@discussions.microsoft.com> wrote:

§ Hey,
§
§ I'm facing a very strange problem.
§ We have a windows application being maintained in CVS (not VSS!!!! and i
§ hate it! but nevertheless....)
§ Within this application, we are connecting to an MS Access database, using
§ the connection string:
§ PROVIDER=Microsoft.Jet.OLEDB.4.0;Data Source=" & strDBPath & ";Password=" &
§ strDBPassword
§ where strDBPath and strDBPassword are being picked up from the config file.
§ Now the project builds alright on all the machines, save for one, where
§ we're getting the following error:
§ "No Error Information Available : VB.NET DB_SEC_E_AUTH_FAILED(0x80040E4D)"
§ This is pretty strange, as due to this error, no form is opening up in the
§ design mode.
§
§ Has anyone faced a similar problem???
§ Tried searching on Google, but there again, it generally comes in when ppl
§ have used very large excessive connection strings, and merely changing the
§ connection string to the version that I am using has rectified the problem in
§ almmost all cases that i browsed through.
§ Any pointers gladly appreciated

If that is your actual connection string then the syntax is incorrect when using a database
password:

http://www.carlprothman.net/Default....orMicrosoftJet
Paul
~~~~
Microsoft MVP (Visual Basic)
Aug 10 '05 #2
Gee thanks Paul for pointing that out!
I was as yet using a DB without a password and that conn string was working
fine.
When i tried using it with a password enabled DB, it couldn't connect. Used
one of the connection strings in that link.

Cheers!
Nick

"Paul Clement" wrote:
On Wed, 10 Aug 2005 00:56:04 -0700, "Nick" <Ni**@discussions.microsoft.com> wrote:

¤ Hey,
¤
¤ I'm facing a very strange problem.
¤ We have a windows application being maintained in CVS (not VSS!!!! and i
¤ hate it! but nevertheless....)
¤ Within this application, we are connecting to an MS Access database, using
¤ the connection string:
¤ PROVIDER=Microsoft.Jet.OLEDB.4.0;Data Source=" & strDBPath & ";Password=" &
¤ strDBPassword
¤ where strDBPath and strDBPassword are being picked up from the config file.
¤ Now the project builds alright on all the machines, save for one, where
¤ we're getting the following error:
¤ "No Error Information Available : VB.NET DB_SEC_E_AUTH_FAILED(0x80040E4D)"
¤ This is pretty strange, as due to this error, no form is opening up in the
¤ design mode.
¤
¤ Has anyone faced a similar problem???
¤ Tried searching on Google, but there again, it generally comes in when ppl
¤ have used very large excessive connection strings, and merely changing the
¤ connection string to the version that I am using has rectified the problem in
¤ almmost all cases that i browsed through.
¤ Any pointers gladly appreciated

If that is your actual connection string then the syntax is incorrect when using a database
password:

http://www.carlprothman.net/Default....orMicrosoftJet
Paul
~~~~
Microsoft MVP (Visual Basic)

Aug 10 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

9 posts views Thread by Tony Lee | last post: by
5 posts views Thread by Nathan Given | last post: by
reply views Thread by justSteve | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.