Importing Access Database to SQL -- "no read permission" on user-level secured DB

I have an old Microsoft Access database that I want to import into MS SQL Server 2000.  I get the following error when I try to run the import:

Error Source:  Microsoft JET Database Engine
Error Description:  Record(s) cannot be read; no read permission on [xxx] (table in old db)

I know the admin user's login and password, but when I enter that information in, I get another error:

Description:  Cannot start your application.  The workgroup information file is missing or is opened exclusively by another user.

I am assuming system.mdw is the "workgroup information file" and have put this everywhere I can think of so that SQL Server could find it.  No such luck so far.

This is urgent... any help is greatly appreciated.
Who is Participating?

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

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.

have you tried opening the access database....
and then linking from access to sql server
and exporting your tables that way?
FunkiNATErAuthor Commented:
Yes, but data transformation never works out and I end up getting error messages as a result.
pegasysIT, System Admin, Development and Stack DevelopmentCommented:
Let me get this straight:

You _can_ open it with access normally and read the file? (y/n)?
You _can_ read while exporting???? (y/n)?


Okay, uhm, have you tried exporting it to another format? Like excel or CSV? It may seem a bit long winded, but its a way around :-)
Excel is usually a foolprro way of (3rd party exporting), I've used it a few times with difficult databases...

IF, you are trying to use an 'ACCESS' drive, in the import wizzard, wather use something like 'Jet', that could work alot better than access drivers..



? should it be the mdb file you "attach" to?
> I am assuming system.mdw is the "workgroup information file" and have put this everywhere
> I can think of so that SQL Server could find it.  No such luck so far.

I suppose you're using the DTS wizard to import the Access Database. So, when you select your Access database as Source, click the Advanced Button (Advanced Connection Properties) and search for the property Jet OLEDB:System Database. As Value of this property, fill in the full path to your WorkGroup file.

After setting the WorkGroup file, fill in username (admin) and password, and try again. Should work.


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
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
Microsoft SQL Server

From novice to tech pro — start learning today.