Solved

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

Posted on 2003-12-04
5
911 Views
Last Modified: 2010-08-05
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.
0
Comment
Question by:FunkiNATEr
5 Comments
 
LVL 50

Expert Comment

by:Lowfatspread
ID: 9878638
have you tried opening the access database....
and then linking from access to sql server
and exporting your tables that way?
0
 

Author Comment

by:FunkiNATEr
ID: 9879296
Yes, but data transformation never works out and I end up getting error messages as a result.
0
 
LVL 7

Expert Comment

by:pegasys
ID: 9879625
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)?

Weird...

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..

Regards

pgx()
0
 
LVL 50

Expert Comment

by:Lowfatspread
ID: 9880733
WHAT SORT OF TRANSFORMATIONS are you attempting?

? should it be the mdb file you "attach" to?
0
 
LVL 7

Accepted Solution

by:
wsteegmans earned 500 total points
ID: 9880930
> 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.

Regards!
0

Featured Post

How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

Join & Write a Comment

I wrote this interesting script that really help me find jobs or procedures when working in a huge environment. I could I have written it as a Procedure but then I would have to have it on each machine or have a link to a server-related search that …
This article explains how to reset the password of the sa account on a Microsoft SQL Server.  The steps in this article work in SQL 2005, 2008, 2008 R2, 2012, 2014 and 2016.
Using examples as well as descriptions, and references to Books Online, show the different Recovery Models available in SQL Server and explain, as well as show how full, differential and transaction log backups are performed
Viewers will learn how the fundamental information of how to create a table.

762 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

15 Experts available now in Live!

Get 1:1 Help Now