Microsoft KB Archive/199931

= ACC2000: The Database Object Does Not Exist Error Message =

Article ID: 199931

Article Last Modified on 1/26/2005

-

APPLIES TO


 * Microsoft Access 2000 Standard Edition

-



This article was previously published under Q199931



Advanced: Requires expert coding, interoperability, and multiuser skills.

This article applies only to a Microsoft Access project (.adp).



SYMPTOMS
If you have a Microsoft Access project (.adp) on a computer that has a different code page setting than the server to which you are linking, and you use characters particular to the code page of the client in the name of an object, you may experience the following behavior:  You cannot view the object in Design view. You see the following errors:

The object ' ' does not exist in the database.

-or-

ADO error: No item by the name of 'dbo.????' could be found in the current database '', given that @itemtype was input as '(null)'.

 You may see no errors with views. However, views may appear blank in Design view. You are permitted to view a database diagram in Design view. If you rename a table, a view, or a stored procedure by using characters particular to the code page of the client computer, the name may be changed to question marks, and you may see the following error:

The database object no longer exists.

 If you name a column in a table with characters from the code page of the client, the column may not display in Datasheet view.

<div class="cause_section">

CAUSE
The code page setting for the keyboard on the server on which Microsoft SQL Server is running is different from the code page setting on the computer that runs the Microsoft Access project (.adp).

<div class="resolution_section">

RESOLUTION
When you create or you rename objects in an Access project (.adp), use a computer that has the same code page as the server.

<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

<div class="moreinformation_section">

Steps to Reproduce the Problem

 * 1) Set up Microsoft SQL server on a computer that runs a U.S.-English version of Microsoft Windows NT, Microsoft Windows 95, or Microsoft Windows 98. (The U.S.-English version always uses the code page 1252 WIN LATIN I, which is also used by Western Europe.)
 * 2) Set up Microsoft Office 2000 on a computer that runs the Greek (or any language version that does not use code page 1252) version of Microsoft Windows or Windows NT.
 * 3) Open Access 2000.
 * 4) On the File menu, click New.
 * 5) In the New dialog box, on the General tab, click Project (Existing Database).
 * 6) In the File New Database dialog box, save the new database project as TestCharacters.adp.
 * 7) In the Data Link Properties dialog box, enter the name of the SQL Server, a valid user name and password, and the database that you want to use. Click OK.
 * 8) In the new Access project, make a copy of any table, and then give the new table a name that uses Greek characters.
 * 9) Try to view the new table in Design view.

Note that you receive one of the errors that are listed in the "Symptoms" section of this article.

Additional query words: pra japanese chinese russian turkish arabic cyrillic slavic int'l international localization localisation globalization

Keywords: kbbug kbfix kbclientserver KB199931

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.