Article ID: 272384 - Last Review: April 17, 2006 - Revision: 8.0 "Overflow" Error Message When You Try to Upsize to SQL Server 2000This article was previously published under Q272384 Moderate: Requires basic macro, coding, and interoperability
skills. This article applies to a Microsoft Access database (.mdb) and to a Microsoft Access project (.adp). On This PageSYMPTOMS When you attempt to upsize a Microsoft Access 2000 database
to Microsoft SQL Server 2000, you may receive the following error message:
Overflow You may also receive the same error message when you try to create an Access project that connects to an instance of Microsoft SQL Server 2000 Desktop Engine (MSDE 2000). RESOLUTIONOffice 2000 Service Pack 3To correct this problem, obtain the latest service pack for Microsoft Office 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:276367
(http://support.microsoft.com/kb/276367/EN-US/
)
OFF2000: How to Obtain the Latest Office 2000 Service Pack
IMPORTANT: Before you install Microsoft Office 2000 Service Pack 3 (SP-3),
you must have Microsoft Office 2000 Service Release 1/1a (SR-1/SR-1a) installed
first.
For additional information about how
to obtain Office 2000 Service Release 1/1a (SR-1/SR-1a), click the following
article number to view the article in the Microsoft Knowledge Base: 245025
(http://support.microsoft.com/kb/245025/EN-US/
)
OFF2000: How to Obtain and Install Microsoft Office 2000 Service Release 1/1a (SR-1/SR-1a) Access 2000 and SQL Server 2000 Readiness Update
Access 2000 and SQL Server 2000 Readiness UpdateMicrosoft has created the "Access 2000 and SQL Server 2000 Readiness Update" to correct this issue. Follow the steps below to obtain and install this update:
NOTE: If you install SQL Server with Windows Authentication Mode set, and later change the Security Authentication to Mixed Mode Authentication, the built-in system administrator (SA) login's password may be blank. After enabling SQL Server security you should immediately create a password for the 'SA' login to help prevent unauthorized access to your SQL Server. For additional information, click the article number below to view the article in the Microsoft Knowledge Base: 274773
(http://support.microsoft.com/kb/274773/EN-US/
)
BUG: If You Change Windows Security to Windows/SQL Security the SA Password is Blank
After SQL Server Authentication is enabled, you can
then use the built-in 'SA' account or create a new SQL Server account for
upsizing. If you are using a new account, be sure to set the "Server Role" to
'Database Creators'. For more information, see SQL Server Books
Online.Work around the Error Without the Readiness UpdateYou can work around the problem by using one of the following methods instead of installing the "Access 2000 and SQL Server 2000 Readiness Update":
STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
at the beginning of this article.
MORE INFORMATION If you previously ran the Upsizing wizard to upsize an
Access 2000 database to SQL Server 7.0, you may encounter another error after
applying this update.
For additional information about this error
message, click the article number below to view the article in the Microsoft
Knowledge Base: 288300
(http://support.microsoft.com/kb/288300/EN-US/
)
ACC2000: Error: "Microsoft Access can't find the wizard..." After Applying the Access 2000 and SQL Server 2000 Readiness Update
Steps to Reproduce Behavior
REFERENCES For information about applying the Access 2000 and SQL
Server 2000 Readiness Update to an administrative installation of Office, click
the article number below to view the article in the Microsoft Knowledge Base:
For
additional information about how you can apply the Access 2000 and SQL Server
2000 Readiness Update to an administrative installation of Office, click the
article number below to view the article in the Microsoft Knowledge Base: 287484
(http://support.microsoft.com/kb/287484/EN-US/
)
OFF2000: Administrative Update Available for Access 2000 and SQL Server 2000 Readiness
| Article Translations
|
Back to the top
