ACC2000: Unable to Import Table When High ANSI Characters Are Used (241232)


The information in this article applies to:

  • Microsoft Access 2000
This article was previously published under Q241232
Advanced: Requires expert coding, interoperability, and multiuser skills.

This article applies only to a Microsoft Access database (.mdb).

SYMPTOMS

When you try to import objects from a Microsoft Access 97 secured database into a Microsoft Access 2000 database, you may receive the following error message:
You don't have permissions to import, export or link to 'tablename'.

CAUSE

The Access 97 workgroup information file was created with high ANSI characters in the Workgroup ID.

RESOLUTION

Workgroups with high ANSI characters do not exhibit this behavior in Microsoft Access 97 databases. The only known workaround at this time is to change the Workgroup ID in Access 97 so that it does not include high ANSI characters.

STATUS

Microsoft has confirmed that this is a problem in Access 2000.

MORE INFORMATION

Steps to Reproduce Behavior

Create a Database in Access 97

  1. Open the Access 97 Workgroup Administrator (Wrkgadm.exe), located in the Windows\System folder.
  2. In the Workgroup Administrator, create a workgroup information file with the following information:
    • UserName: JoeDoe
    • Company: TEST
    • For the Workgroup ID, use the following high ANSI characters:

      • ALT+0182
      • ALT+0224
      • ALT+0188
      • ALT+0196
      • ALT+0194
      • ALT+0201

  3. Start Access and open the Access 97 sample database Northwind.mdb.
  4. Create a new user account with the UserName: JoeDoe and add the JoeDoe user account to the ADMINS Group.

    For the Personal ID (PID), use the following high ANSI characters:
    • ALT+0182
    • ALT+0192
    • ALT+0200
    • ALT+0201

  5. Quit Access, restart it, and log on by using the new JoeDoe user account with no password.
  6. Remove the Admin user from the ADMINS group.
  7. Create a new group called Acc97 with the following high ANSI characters for the PID:
    • ALT+0182
    • ALT+0183
    • ALT+0184
    • ALT+0185

  8. Create another new group called Acc97NoHANSI with a PID of 1234.
  9. Create a new database called DB1.mdb.
  10. Import all the tables from Northwind.mdb into DB1.mdb.
  11. Using the User-Level Security Wizard, secure DB1.mdb. Name it Secure DB1.mdb.
  12. Open the newly secured Secure DB1.mdb.
  13. Give both of the new groups Administer permissions to all the tables, including the system tables.
  14. Give both of the new groups Open Run, Open Exclusive, and Administer rights to the database. At this point, both groups should be identical, except for the fact that one has a PID of high ANSI characters.
  15. Quit Access 97.

Open the Database in Access 2000

  1. Use the Access 2000 version of Workgroup Administrator to create a new workgroup information file. Use the UserName, Company, and Workgroup ID that you used in step 2 of the "Create a Database in Access 97" section.
  2. Start Access 2000 and create a new user called Joe2000 with the following high ANSI characters for the PID:
    • ALT+0182
    • ALT+0192
    • ALT+0200
    • ALT+0201

    NOTE: These are the same high ANSI characters used to create the group in Access 97.

  3. Create a new group called Acc97 with the following high ANSI characters for the PID:
    • ALT+0182
    • ALT+0183
    • ALT+0184
    • ALT+0185

  4. Create another new group called Acc97NoHANSI with a PID of 1234.NOTE: This also is the same name and PID used with Access 97.

  5. Make Joe2000 a member of the group Acc97.
  6. Give Admin a password.
  7. Quit Access 2000 and restart it.
  8. Log on as Joe2000 and create a new database.
  9. On the File menu, point to Get External Data, and then click Import.
  10. Select the Secure DB1.mdb and try to import a table.
  11. Note that you receive the error message:
    You don't have permissions to import, export or link to 'tablename'
  12. If you move the Joe2000 user account to the Acc97NoHANSI group, you can import the objects, and you won't receive the error message.

REFERENCES

For additional information about errors you may encounter converting a database, please click the article number below to view the article in the Microsoft Knowledge Base:

232589 ACC2000: "The Current User Account Doesn't Have Permission to Convert or Enable This Database" Error Message

Modification Type:MinorLast Reviewed:1/26/2005
Keywords:kbbug kbpending KB241232
©2004 Microsoft Corporation. All rights reserved.