Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1046
  • Last Modified:

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.
0
FunkiNATEr
Asked:
FunkiNATEr
1 Solution
 
LowfatspreadCommented:
have you tried opening the access database....
and then linking from access to sql server
and exporting your tables that way?
0
 
FunkiNATErAuthor Commented:
Yes, but data transformation never works out and I end up getting error messages as a result.
0
 
pegasysCommented:
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
 
LowfatspreadCommented:
WHAT SORT OF TRANSFORMATIONS are you attempting?

? should it be the mdb file you "attach" to?
0
 
wsteegmansCommented:
> 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

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now