UT1x: Upsizing Wizard Incorrectly Converts Extended Characters

 Last reviewed: May 27, 1997
Article ID: Q124409
The information in this article applies to:
  • Microsoft Access Upsizing Tools version 1.0

SYMPTOMS

When you use the Microsoft Access Upsizing Tools Upsizing Wizard to transfer tables from Microsoft Access version 2.0 to Microsoft SQL Server, certain extended ASCII characters in table or field names are not transferred as underscore characters as they should be. When the Upsizing Wizard creates items such as triggers, rules, and defaults for these tables or fields, however, it refers to the underscore character that should have been used, instead of to the extended character. For example, if you have a table with a counter field named 

   <accented A>bracadabra
the INSERT trigger will reference the field as 

   _bracadabra
even though the field will still be named: 

   <accented A>bracadabra

RESOLUTION

To work around this problem, replace the extended characters in table or field names with an underscore character in Microsoft Access before you transfer the tables to Microsoft SQL Server. Characters with a value greater than 128 can exhibit this problem.

STATUS

Microsoft has confirmed this to be a problem in the Microsoft Access Upsizing Tools version 1.0. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Keywords : AutPrb kbusage
Version : 1.0
Platform : WINDOWS
Hardware : X86
Issue type : kbbug
Resolution Type : kbworkaround

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: May 27, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.