Article ID: 328019 - View products that this article applies to.
This article was previously published under Q328019
This article has been archived. It is offered "as is" and will no longer be updated.
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:
(http://support.microsoft.com/kb/256986/ )Description of the Microsoft Windows Registry
When you use the Upsizing Wizard in Microsoft Access 2002 to upsize a database to SQL Server, you notice that descending indexes change to ascending indexes in the resulting database.
Note This issue occurs even after you install Microsoft Office XP Service Pack 2 (SP-2) or Microsoft Office XP Service Pack 3 (SP3). The fix for this issue is documented as being fixed in Office XP SP-2. For additional information about the issue that is described in the "Symptoms" section of this article, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/325670/ )List of issues fixed in Access 2002 by Office XP Service Pack 2
This issue may occur when you run the Upsizing Wizard, and then later you install Office XP SP-2 or Office XP SP3. As part of the Office XP SP-2 or Office XP SP3 update process, versioned files that are not user-modified are updated. If you run the Upsizing Wizard, the versioned files that are associated with the wizard are modified and Office XP SP-2 and SP3 treat them as unversioned user-modified files and may not be able to update them correctly.
To resolve this issue, download and install the Access 2002 Update: KB833857. For additional information about the Access 2002 Update: KB833857, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/833857/ )Description of Microsoft Access 2002 Update: March 23, 2004
Administrative informationIf you are an administrator, there are additional methods that you can use to resolve this issue. Database administrators may deploy Office XP Service Pack 2 or Office XP Service Pack 3 by using the method that is described in the service pack literature on the Office Resource Kit (ORK), and then follow these steps for user systems that run Access 2002.
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. Locate your GUID number, and then run Msiexec.exe. To do so, follow these steps:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.
After Office XP SP-2 is installed and the Access 2002 wizard files have been updated by using the Msiexec.exe utility, the wizard files must have the following file attributes or later:
Date Time Size File name ---------------------------------------------------- 05-Dec-2001 04:46 1,662,976 Acwzlib.mde 05-Dec-2001 04:46 5,345,280 Acwzmain.mde 25-Apr-2002 02:03 8,019,968 Acwztool.mde
For additional information about GUID numbers and the Msiexec.exe utility, click the following article number to view the article in the Microsoft Knowledge Base:
302663For additional information about Office XP Service Pack 2 in the service pack literature on the Office Resource Kit (ORK), visit the following Microsoft Web site:
(http://support.microsoft.com/kb/302663/ )OFFXP: Numbering Scheme for Product Code GUIDs
http://www.microsoft.com/office/ork/xp/journ/oxpsp2a.htmFor additional information about Office XP Service Pack 3 in the service pack literature on the Office Resource Kit (ORK), visit the following Microsoft Web site:
(http://go.microsoft.com/fwlink/?LinkId=151500)for other considerations.