Article ID: 328319 - View products that this article applies to.
This article was previously published under Q328319
This article has been archived. It is offered "as is" and will no longer be updated.
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
This article contains links to other articles about issues that you may experience when you upsize a database in Microsoft Access.
For 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:
(https://support.microsoft.com/kb/295231/EN-US/ )ACC2002: Upsizing Wizard Fails to Upsize Data in Large Tables
(https://support.microsoft.com/kb/295235/EN-US/ )ACC2002: The Upsizing Wizard Does Not Upsize Nested Queries If Base Queries Are Upsized as Functions
(https://support.microsoft.com/kb/294398/EN-US/ )ACC2002: Tables Not Upsized When Query or Table Name Contains Apostrophe
(https://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
(https://support.microsoft.com/kb/294923/EN-US/ )ACC2002: Cannot Use Upsized Append Queries in an Access Project
(https://support.microsoft.com/kb/282390/EN-US/ )ACC2002: "Server Error 134" Error Message When You Attempt to Upsize Your Database
(http://go.microsoft.com/fwlink/?LinkId=151500)for other considerations.