Article ID: 328319 - Last Review: August 2, 2004 - Revision: 3.1 List of issues with upsizing wizard in Access 2002This article was previously published under Q328319 Moderate: Requires basic macro, coding, and interoperability
skills. This article applies only to a Microsoft Access database (.mdb). For a Microsoft Access 2000 version of this article, see 325019 (http://support.microsoft.com/kb/325019/EN-US/ ) . SUMMARY This article contains links to other articles about issues
that you may experience when you upsize a database in Microsoft Access.
MORE INFORMATIONFor additional information about
problems that you may experience when you upsize a database, and resolutions or
workarounds to those problems, click the article numbers below to view the
articles in the Microsoft Knowledge Base: 295231
(http://support.microsoft.com/kb/295231/EN-US/
)
ACC2002: Upsizing Wizard Fails to Upsize Data in Large Tables
295235
(http://support.microsoft.com/kb/295235/EN-US/
)
ACC2002: The Upsizing Wizard Does Not Upsize Nested Queries If Base Queries Are Upsized as Functions
294398
(http://support.microsoft.com/kb/294398/EN-US/
)
ACC2002: Tables Not Upsized When Query or Table Name Contains Apostrophe
282380
(http://support.microsoft.com/kb/282380/EN-US/
)
ACC2002: Bad File Name or Number Error Message When You Upsize Databases with Data Access Pages Stored on Server
294923
(http://support.microsoft.com/kb/294923/EN-US/
)
ACC2002: Cannot Use Upsized Append Queries in an Access Project
282390
(http://support.microsoft.com/kb/282390/EN-US/
)
ACC2002: "Server Error 134" Error Message When You Attempt to Upsize Your Database
| Article Translations
|
| United States | Change | | | All Microsoft Sites |
Back to the top
|
