Microsoft KB Archive/282390

= ACC2002: &quot;Server Error 134&quot; Error Message When You Attempt to Upsize Your Database =

Article ID: 282390

Article Last Modified on 5/30/2006

-

APPLIES TO


 * Microsoft Access 2002 Standard Edition

-



This article was previously published under Q282390



IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry

Moderate: Requires basic macro, coding, and interoperability skills.

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



SYMPTOMS
When you attempt to upsize your database, you may receive an error message similar to the following:

Server Error 134: The variable name '@Forms......' has already been declared. Variable names must be unique within a query batch or stored procedure.

Server Error 170: Line 7: Incorrect syntax near ')'.



CAUSE
This behavior can occur if queries in your database contain parameters that match through the first 30 characters. For example, the following query produces the error message:   PARAMETERS [123456789012345678901234567890start] DateTime,    [123456789012345678901234567890end] DateTime; SELECT item, date FROM Table1 WHERE date Between [123456789012345678901234567890start] And   [123456789012345678901234567890end]; Note that this query contains two parameters that match each other through the first 30 characters:
 * [123456789012345678901234567890start] DateTime
 * [123456789012345678901234567890end] DateTime



RESOLUTION
To resolve this issue, change the parameter names in such a way that they differ within the first 30 characters. For example, if your query contains the following two parameters
 * [123456789012345678901234567890start] DateTime
 * [123456789012345678901234567890end] DateTime

you can change the parameters to the following:
 * [start123456789012345678901234567890] DateTime
 * [end123456789012345678901234567890] DateTime

Note that the Upsizing Wizard accepts only the first 30 characters, so the resulting SQL query contains the following parameters:
 * (@start1234567890123456789012345) DateTime
 * (@end123456789012345678901234567) DateTime



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



MORE INFORMATION
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

Steps to Reproduce the Problem
 Start the Registry Editor (Regedit.exe). Open the following registry key:

HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Access\Wizards\Preferences\Upsizer\Quiet

 Set the value of this key to No, and then close the Registry Editor. Start Microsoft Access, and then create a new database, Db1.mdb.</li>  Create a new table in Db1.mdb: <pre class="fixed_text">  Table: Table1 --  Field Name: ID   Data Type:  Text PrimaryKey: Yes

Field Name: Date Data Type: Date/Time

Field Name: Item Data Type: Text </li> In the Database window, click Queries, and then double-click Create a new query in design view.</li> Click Close, and then click SQL on the Query Design toolbar.</li>  In the SQL Editor, enter the following query: <pre class="fixed_text">  PARAMETERS [123456789012345678901234567890start] DateTime,    [123456789012345678901234567890end] DateTime; SELECT item, date FROM Table1 WHERE date Between [123456789012345678901234567890start] And   [123456789012345678901234567890end]; </li> Save the query as qryLongParameters, and then close the SQL Editor.</li> On the Tools menu, point to Database Utilities, and then click Upsizing Wizard.</li> Upsize your database to SQL Server.

You receive an error message similar to the one listed in the &quot;Symptoms&quot; section of this article.</li></ol>

<div class="references_section">