Using a Secured Access database in SQL 2000

  • I need to export some tables from an Access 2003 database and it is password-protected.  When I use the Access connection in the DTS package I give it the filename path and the username is admin.  I give it the password and it complains that it can't find the Workgroup Information File.  No problem, or so I think.  I get the system.mdw file from the PC that password-protected the .mdb and I modify the registry entry on the SQL Server box to point to this system.mdw file.  I think everything is great now.  Now when I use the Access connection and give it the password it complains that it is not either a valid username or password.  I don't know whatelse to do at this point.  Does anybody know how to access and Access database from SQL that is password-protected.  The user will not take the password off so I have to figure out something.  Thanks for any help in advance

    Gary

  • This was removed by the editor as SPAM

  • I'm guessing you already tried the good old Admin, blank password default?  Also, you might check and make sure that it's actually the system.mdw that is protecting the db.  It might be another one the user has created...

    To help us help you read this[/url]For better help with performance problems please read this[/url]

  • When I go into Access I get prompted for the password.  I enter it and I can get right into the database no problem.  The problem is accessing the .mdb that sits on a shared network drive from the SQL database using DTS.  When I setup the Access connection object in DTS iand point it to the .mdb file it asks for username which is Admin and then password.  I type in the password and the error is: Missing Workgroup information file or locked for exclusive use.  I copied the system.mdw file from the users PC and modified the registry on the SQL-Server box to point to the .mdw file and when I type in the password in DTS is says the password is invalid.  When I have the user rename the system.mdw file on the PC then you can't get into Access using the password as it complains that the Workgroup information file is missing or locked for exclusive use.  This tells me that it is the correct file protecting the .mdb.

  • yep, that's the right file then... any chance you could create a DSN that points to the access db?  Then use the DSN fo ryour DTS connection instead of a direct connection to the access db.

    To help us help you read this[/url]For better help with performance problems please read this[/url]

  • I am going to try using a DSN as I am not getting anywhere.  I'll let you know how/if it works.  Thanks for your input.

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply