jitu_r_soni
asked on
VB6/Access Connection Opening
Hi All Experts,
I have developed one application using VB6/Access 2000 platform. In that, I have secured the database by using "Set Database Password...". I can open this Password protected database connection using following string.
.provider = "Microsoft.Jet.OLEDB.4.0;"
.properties{"Jet.OLEDB:Pas sword"}="p assword"
.open app.path & "\filenm.mdb"
Now my problem is when I run this application on MS Access 2003 XP Professional, it gives an error for "not valid password" & also gives an error for ".Provider". Actually ".provider" property doesn't support.
I will be very thankful if somebody can give the best solution.
Thanks in advance.
I have developed one application using VB6/Access 2000 platform. In that, I have secured the database by using "Set Database Password...". I can open this Password protected database connection using following string.
.provider = "Microsoft.Jet.OLEDB.4.0;"
.properties{"Jet.OLEDB:Pas
.open app.path & "\filenm.mdb"
Now my problem is when I run this application on MS Access 2003 XP Professional, it gives an error for "not valid password" & also gives an error for ".Provider". Actually ".provider" property doesn't support.
I will be very thankful if somebody can give the best solution.
Thanks in advance.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Here's an article that might be of interest to you:
http://support.microsoft.com/kb/303528/
Could it be the version of MDAC that it was compiled with ?!?!?
I know 2.6 and higher don't include the access odbc driver, but that doesn't seem to be the issue here.
Going back to DAO definitely isn't the answer! ;)
http://support.microsoft.com/kb/303528/
Could it be the version of MDAC that it was compiled with ?!?!?
I know 2.6 and higher don't include the access odbc driver, but that doesn't seem to be the issue here.
Going back to DAO definitely isn't the answer! ;)
YourConn.Open "Provider=Microsoft.Jet.OL
& ";Jet OLEDB:Database Password=password;"