Microsoft Office Online
Sign in to My Office Online (What's this?) | Sign in

 
 
Office 2000 Resource Kit
Search
Search
 
Check for updates: (c) Microsoft
Office downloads
 
 
 
Versions
Table of Contents
 

Warning: You are viewing this page with an unsupported Web browser. This Web site works best with Microsoft Internet Explorer 6.0 or later, Firefox 1.5, or Netscape Navigator 8.0 or later. Learn more about supported browsers.

Email this linkEmail this link Printer-Friendly VersionPrinter-Friendly Version Bookmark and ShareShare
Access 2000/SQL Server 2000 Readiness Update
 

The administrative version of the Access 2000/SQL Server 2000 Readiness Update improves the way in which Microsoft Access 2000 works with Microsoft SQL Server 2000. This update allows you to upsize Access databases to SQL Server 2000, and to create new databases against SQL Server 2000 using an Access project. When designing SQL Server 2000 objects, this update will enable you to use Access 2000 to create and edit the design of tables, views, and stored procedures using an Access project.


 Note   To use the Access 2000/SQL Server 2000 Readiness Update, you must first upgrade your computers to Office 2000 Service Release 1a (SR-1a).



Toolbox   The administrative version of the Access 2000/SQL Server 2000 Readiness Update consists of two Windows Installer patch files (MSP format) packaged in one self-extracting executable. You can find this downloadable file on the Office 2000 Resource Kit Downloads page.


Applying the Access 2000/SQL Server 2000 Readiness Update to an administrative installation point

You apply the Access 2000/SQL Server 2000 Readiness Update files to your administrative share by using a command line with specific parameters. Both MSP files are required to update the Access and SQL Server components on your computers. The following table lists the MSP file names.

MSP file name Description
ACWZ_Admin.msp Windows Installer update for the Access 2000 components.
MDT2_Admin.msp Windows Installer update for the SQL Server 2000 components.


 Note   For best results, the update files should be applied from the console of the computer containing the administrative installation point. Please ensure that the files on the share point are not in use when the updates are being applied. If there are multiple administrative installation points, you may replace the remaining administrative installation points with the updated administrative installation point after backing-up any custom transform, Setup.ini, or other files on the share points.


To apply the Access 2000/SQL Server 2000 Readiness Update to an administrative installation point

  1. Download Accsql_a.exe and double-click the file name to extract the two administrative update files. Refer to the table above for the file names and descriptions.
  2. Connect to the server share for the administrative installation point.

    You must have write access to the administrative installation point on the server and the appropriate privileges to carry out the task.

  3. On the Start menu, click Run and then type the command line for Windows Installer with the appropriate options for the Access 2000/SQL Server 2000 Readiness Update. Use the following syntax:

    [start] msiexec /p [path\name of update MSP file] /a [path\name of MSI file] SHORTFILENAMES=TRUE /qb /L* [path\name of log file]

You will need to run the command line separately for each MSP file you apply to the administrative installation point — you cannot reference multiple MSP files on the same command line. The following table describes the command-line options.

Command-line option Description
[start] Required only for Windows 95 or 98 systems where Msiexec is not directly in the path.
msiexec Executable file name for Windows Installer.
/p Enables Windows Installer to apply an update to an existing installation.
[path\name of update MSP file] Path and file name of the MSP file for the files you want to update. For a list of MSP file names, refer to the table earlier in this document.
/a Enables Windows Installer to perform an administrative installation of a product on a network share.
SHORTFILENAMES=TRUE Directs Windows Installer to create all file names and folders with MS-DOS compatible file names, as used on Office 2000 Disc 1. Required when you run Windows Installer from the command line.
/qb Sets the user interface to the basic level (simple progress and error handling). This switch is optional on the command line.
/L* Turns on logging and sets a path for the log file. The * flag causes the switch to log all information. This switch is optional on the command line.
[path\name of log file] Path and file name of the Windows Installer log file.

Updating client computers from an administrative installation point

After you update your administrative installation point, you must perform a recache and repair on existing client computers that use the administrative image. Any new client installations from the administrative installation point will automatically include the updated versions of Access 2000 and SQL Server 2000.

To update an existing client installation from an administrative installation point, run the following command line on the client computer:

start msiexec /i [path to updated .msi file on the administrative image] REINSTALL=[list of features] REINSTALLMODE=vomus UPGRADEWITHRECACHE=TRUE /q

You can run this command line by creating a log-on script, distributing it as a batch file, deploying it via Systems Management Server, or using other means according to your practice. The options for this command line are as follows.

Command-line option Description
[start] Required only for Windows 95 or 98 systems where Msiexec is not directly in the path.
Msiexec Executable file name for Windows Installer.
/I Enables Windows Installer to apply an update to an existing installation.
[path to updated .msi file on the administrative image] Path and file name of the Microsoft Installer (.MSI) file on the administrative installation point.
REINSTALL =[list of features] Specifies whether you want to reinstall specific features or reinstall all applications on the administrative image.
REINSTALLMODE=vomus Triggers the recache and reinstallation on the client computer.
UPGRADEWITHRECACHE=TRUE Required to properly update the Microsoft SQL Server support files. This property causes the End User License Agreement acceptance dialog to appear.
/q Suppress the End User License Agreement dialog box so Administrators or end-users will not be prompted by this dialog box.

For the Access 2000/SQL Server 2000 Readiness Update, the variable [list of features] should be replaced with the following value:

REINSTALL=ACCESSFiles,AccessWizards,DeveloperWizards,ACCESSNonBootFiles,OfficeWebComponents,MSVisualDesignTool,ACCESSNonBootFiles

Due to the length of this value, the full command line may not fit on the Start/Run command line. To work around this limit, you can paste the command line into a command prompt. Optionally, you can substitute the parameter REINSTALL=ALL to reinstall all components on the client computer.


 Note   If you originally installed Office 2000 on a client computer from an administrative installation point, you must follow the recache and repair procedure described above to update that client. If you update the client directly by using the end-user patch from the Office Update Web site, the client and administrative images will become out-of-sync, which may cause future updates to fail.


Applying the Access 2000/SQL Server 2000 Readiness Update under Windows 2000

If your administrative installation point and all of your client computers are running Windows 2000, you can use IntelliMirror® technology to manage the installation of the security update.


 Note   Be sure to test all software updates in a controlled setting before modifying your administrative installation point or deploying the new version throughout your organization.


To deploy a QFE fix or update under Windows 2000

  1. Apply the updates (MSP files) to the original Office administrative installation point.

    You will need to run the command line separately for each MSP file you apply to the administrative installation point — you cannot reference multiple MSP files on the same command line.

  2. Open the Software Installation snap-in within the Group Policy Object (GPO) that you are using to manage the existing Office installation.
  3. In the details pane, right-click the Office package, point to All Tasks, and click Redeploy application.
  4. The next time the Group Policy is applied to the designated users or computers, the updated files are copied to their computers.

 Note   You can redeploy a package only if it is being managed by Group Policy — that is, only if you originally installed it by using IntelliMirror software installation and maintenance or if you brought it into a managed state under Windows 2000.


Related links

For information on deploying the Office 2000 SR-1a Update, see Deploying Office 2000 Service Release 1 in the Office Resource Kit Journal. For information on the version of the Access 2000/SQL Server 2000 Readiness Update for stand-alone computers, see Office 2000 Update: Service Pack 3 (SP3) .

advertisement