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:Password"}="password"
.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.
jitu_r_soniAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

pradapkumarCommented:
Are you able to connect thru ADODB Active X control?
If so, try to Build COnnection string from there if it succeeded the test then copy the exact connection string from there to your project.

Wish u all the best.
N.Pradap Kumar

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
leclairmCommented:
Try:

YourConn.Open "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" app.path & "\filenm.mdb"
 & ";Jet OLEDB:Database Password=password;"
leclairmCommented:
Sorry, forgot an "&"

YourConn.Open "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" & app.path & "\filenm.mdb"
 & ";Jet OLEDB:Database Password=password;"
abdulhameedsCommented:
try this

Public ACCDB As Database
Public GLLCSYSDB As Database

 GL_pBDbs = "c:\" & "ACCOUNT.mdb"
     GL_pBDbs1 = "c:\" & "ACCOUNT.mdb"
   Set ACCDB = Workspaces(0).OpenDatabase(GL_pBDbs, False, False, ";pwd=ACC1999")
   Set GLLCSYSDB = Workspaces(0).OpenDatabase(GL_pBDbs1, False, False, ";pwd=ACC1999")

i use it in my application
leclairmCommented:
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! ;)
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Visual Basic Classic

From novice to tech pro — start learning today.