You can use any of the following three methods to resolve
this problem:
- Method 1: Re-create the User Database by Using the Default
Collation of SQL Server
- Method 2: Rebuild the Master Database or Reinstall SQL
Server by Using the Same Collation as the User Database
- Method 3: Reinstall the Version of the Visual Database
Tools that Were Included with Office XP
Method 1: Re-create the User Database by Using the Default Collation of SQL Server
You can only specify the collation of a database when it is
created. Because Access always creates new databases by using the default
collation of SQL Server, the easiest way to solve the problem is to have Access
create a new database on the server and then to import the objects from your
current database into the new database. To do so, follow these steps.
Microsoft
Office Access 2003 and earlier versions of Access
- Start Microsoft Access, and then click New on the File menu.
- In the New File task pane, click Project (New Data).
- To give your project a new name and to save it to your
folder of choice, click Create in the File New Database dialog box.
- Use the Microsoft SQL Server Database wizard to specify the
server settings, and then use the wizard to create and connect to your new
database.
- On the File menu, point to Get External Data, and then click Import.
- In the Import wizard, select the project you were
previously using to connect to SQL Server, and then click Import.
- Click Select All on each tab to select all of the objects.
- To import the selected items into the new file, click OK. You may get collation errors during the import
process.
After the import is complete, you can open tables without
error. You may also have to re-create relationships, other SQL Server objects,
and properties that were not imported.
Microsoft Office Access 2007- Start Access, click the Microsoft Office Button, and then
click New.
- In the File Name box, type
ProjectName.adp, and then
click Create.
- Click No to create a new SQL Server
database.
- Use the Microsoft SQL Server Database Wizard to specify the
server settings, and then use the wizard to create and connect to your new
database.
- Click the External Data tab, and then
click Access in the Import group.
- In the Import Wizard, select the project you were
previously using to connect to SQL Server, and then click Import.
- Click Select All on each tab to select all of the objects.
- To import the selected items into the new file, click OK. You may experience collation errors during the import
process.
After the import process is completed, you can open tables without
error. You may also have to re-create relationships, other SQL Server objects,
and properties that were not imported.
Method 2: Rebuild the Master Database or Reinstall SQL Server by Using the Same Collation as the User Database
SQL Server 2000 comes with a utility named rebuildm.exe that you
can use to create a new Master database with a different collation. You can
also specify a custom collation option when you install SQL Server. However,
the rebuildm.exe utility does not come with SQL Server 2000 Desktop Engine.
Also, there is also no graphical utility that you can use to select a collation
option when you install the Desktop Engine. You must modify the Setup.ini file
to specify a custom collation for the Desktop Engine. To learn how to do this,
click the article number below to view the article in the Microsoft Knowledge
Base:
301413 ACC2002: "Configuring SQL Server 2000 Desktop Engine" White Paper Available in Download Center
Method 3: Reinstall the Version of the Visual Database Tools that Were Included with Office XP
- Remove Visual Studio. NET.
- Find and rename the Visual Database Tools folder. By default, this folder is installed to the following
location:
C:\Program Files\Common Files\Microsoft Shared\Visual Database Tools
- Start Access.
- To reinstall the files in the renamed Visual Database Tools
folder, click Detect and Repair on the Help menu.NOTE: Although you can fix the problem in Access by following steps 2
through 4, this is not a good idea because you may experience additional
problems with Server Explorer in Visual Studio. NET.