Description of the Access 2003 post-Service Pack 2 hotfix package: January 24, 2006

Article translations Article translations
Article ID: 902445 - View products that this article applies to.
Expand all | Collapse all

On This Page

SUMMARY

Microsoft has released the Microsoft Office Access 2003 post-Service Pack 2 hotfix package for Access 2003.
This article describes the following items about the hotfix package:
  • The issues that the hotfix package fixes.
  • The prerequisites for installing the hotfix package.
  • Whether you must restart your computer after you install the hotfix package.
  • Whether the hotfix package is replaced by any other hotfix package.
  • Whether you must make any registry changes.
  • The files that the hotfix package contains.

INTRODUCTION

This article describes the Access 2003 issues that are fixed in the hotfix package that is dated January 24, 2006.

Issues that the hotfix package fixes

This hotfix package fixes the following issue:
913545 The first lines or the last lines of some report pages may not appear or may be truncated in Access 2003
This hotfix package fixes the following issues that were not previously documented in a Microsoft Knowledge Base article:
  • Access 2003 closes unexpectedly, and you receive a "Microsoft Office Access has encountered a problem and needs to close" error message when you click Clear Grid to try to clear a form

    Consider the following scenario. You click Filter by Form in an Access 2003 form, select a value in the form, and then click Apply Filter to apply the filter. After you repeat this procedure several times, you click Clear Grid. However, the form is not cleared as expected. Instead, you receive the following error message, and then Access 2003 closes unexpectedly:
    Microsoft Office Access has encountered a problem and needs to close. We are sorry for the inconvenience.
  • You receive a "The expression you entered has a function name that Microsoft Access cannot find" error message when you run a macro that references the Utility.mda file

    Consider the following scenario. You create a function in a module. The name of the function starts with a double-byte character set (DBCS) character. Then, you create a macro that runs the function. Additionally, you add a reference to the Utility.mda file. When you run the macro, you receive the following error message:
    The expression you entered has a function name that Microsoft Access cannot find.
  • You receive a "Run-time error '3078': The Microsoft Jet database engine can't find the input table or query 'TableName(dbo)'" error message when you try to use the TransferSpreadsheet method

    When you try to use the TransferSpreadsheet method in a Microsoft Access project (.adp) if you are not connected to the database as the database owner (dbo), you receive the following error message:
    Run-time error '3078': The Microsoft Jet database engine can't find the input table or query 'TableName(dbo)'. Make sure it exists and that its name is spelled correctly.
  • Duplicate values appear in the group header or group footer section of a report when you print or view the print preview of a report

    When you print a report, or when you view the print preview of a report, duplicate values may appear in the group header or group footer section of the report. You experience these symptoms even though the HideDuplicates property for the control is set to Yes.
  • Access 2003 closes unexpectedly when you print a report and then scroll through the report

    When you print a report and then scroll through the report, Access 2003 closes unexpectedly. This problem may occur if the report is bound and has a subreport that contains an ActiveX control.
  • You receive a "Run-time error '5': Invalid Procedure call or Argument" error message when you try to set the PaperBin property to a value that is more than 256

    In Visual Basic Editor, you can only set the PaperBin property to a value of 256 or less. When you try to set the PaperBin property to a value that is more than 256, you receive an error message that is similar to the following:
    Run-time error '5':
    Invalid Procedure call or Argument.
  • You receive a "This document was previously formatted for the printer PrinterName on Port; but that printer isn't available" error message when you programmatically change the printer selection

    When you use code to change the printer selection to a printer that is not the default printer in an Access 2003 report, you may receive an error message that is similar to the following:
    This document was previously formatted for the printer PrinterName on Port; but that printer isn't available. Do you want to use the default printer DefaultPrinterName on Port
    This issue occurs if the following conditions are true:
    • The report was originally saved with the Use Specific Printer option set to Default printer.
    • You use a script to change the selected printer to a printer that is not the default printer.
    When you use a script to change the selected printer, the UseDefaultPrinter property is not set to False.
  • Access 2003 SP2 closes unexpectedly (crashes) when you change printer settings in the Page Setup dialog box for a report several times

    You click a report in the Database window and then click Page Setup on the File menu to open the Page Setup dialog box. When you change printer settings in the Page Setup dialog box several times, Access 2003 SP2 closes unexpectedly (crashes).
  • The Microsoft Windows XP theme is not applied to forms in a Microsoft Access project (.adp) that is referenced by another Microsoft Access project

    When you use a Microsoft Access project (.adp) that references another Microsoft Access project, the Windows XP theme is not applied to forms in the referenced Microsoft Access project. This problem occurs when you reference the other Microsoft Access project by using the References dialog box in Visual Basic Editor.
  • A record may unexpectedly be saved when certain Microsoft Windows settings are changed

    A record may unexpectedly be saved when certain Windows settings are changed. For example, if you are adding or changing a record when a Group Policy setting is applied to the computer, the record is unexpectedly saved.
  • You receive a "Microsoft Access can't represent the join expression" error message when use Access 2003 to open a query that was created in an earlier version of Access

    When you use Access 2003 to open a query that was created in an earlier version of Access, you may receive the following error message:
    Microsoft Access can't represent the join expression
    When you copy the query and then paste the query in the database window by using a new name for the query, you find that the join is dropped from the query. Therefore, the query no longer works correctly.
  • Access 2003 SP2 closes unexpectedly (crashes) when you try to compact the database

    Access 2003 SP2 may close unexpectedly (crash) when you try to compact the database in any one of the following scenarios:
    • Code is compiled. You open and close the Visual Basic IDE. Then, you run the Compact and Repair Database utility.
    • Code is compiled. You open and close the Visual Basic IDE. You choose to perform a compact on close and then close the database.
    • Code is compiled. You open and close the Visual Basic IDE. You choose not to perform a compact on close and then close the database. Then, you compact the database from the command line.

MORE INFORMATION

Service pack information

This problem was first corrected in Office 2003 Service Pack 3. To resolve this problem, obtain the latest service pack for Office 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
870924 How to obtain the latest service pack for Office 2003

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

The following list contains prerequisites for the hotfix package:
  • The optimized version of this hotfix is a post-Microsoft Office 2003 Service Pack 2 hotfix. To install the hotfix, you must have Office 2003 Service Pack 2 installed. For more information about Office 2003 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
    887616 Description of Office 2003 Service Pack 2
  • The full-file version of this hotfix is also the administrative version of this hotfix. You can install this version of the hotfix on a computer that is running Office 2003 with Service Pack 2 installed or Office 2003 with Service Pack 1 installed. However, we have tested this hotfix more extensively on Office 2003 with Service Pack 2 than we have on Office 2003 with Service Pack 1. If you install this hotfix on a computer that is running Office 2003 with Service Pack 1, some file conflicts might occur. We support this configuration, but we do not recommend this configuration.

Restart information

You do not have to restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix is not replaced by any later hotfix.

Registry information

You do not have to create any registry keys or modify any registry keys to use any hotfixes that this package contains.

Hotfix file information

This hotfix may not contain all the files that you must have to fully update a product to the latest build. This hotfix contains only the files that you must have to correct the issues that this article lists.

The global version of this hotfix uses a Microsoft Windows Installer package to install the hotfix. The dates and times for these files are listed in coordinated universal time (UTC) in the following table. When you view the file information, the date is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

Download information
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Office2003-kb902445-glb.exe4,450,55210-Feb-200600:12x86

Microsoft Windows Installer .msp file information
Collapse this tableExpand this table
File nameFile versionFile sizeDateTime
Msaccessff.mspNot applicable20,303,87224-Jan-200603:43
Msaccessop.mspNot applicable1,839,10423-Jan-200623:05
Thumbs.dbNot applicable4,09621-Dec-200523:37
After the hotfix package is installed, the global version of this hotfix package has the file attributes, or later file attributes, that are listed in the following table.
Collapse this tableExpand this table
File nameFile versionFile sizeDateTime
Facxlisamreg.mstNot applicable14,33613-Jun-200521:59
Msaccess.exe11.0.8008.06,658,24810-Jan-200600:41
Msaexp30.dll11.0.6561.0133,32003-Jun-200519:45
Mscdm.dll11.0.6550.0231,61617-Mar-200521:40
Notes
  • For more information about how to install this hotfix, see the Readme.txt file that is included in the hotfix package.
  • For more information about the differences between the two .msp files, see the "Strategies for Updating Office 2003 Installations" topic. To see this topic, visit the following Microsoft Web site:
    http://office.microsoft.com/en-us/ork2003/HA011525741033.aspx
For more information about the terminology that is used to describe Microsoft software updates, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Known issues

  • When you install Access 2003 SP2, you may experience the issue that is described in the following article in the Microsoft Knowledge Base:
    914830 Access 2003 may not start as expected after you install Office 2003 SP2
    Because of this issue, some large enterprise customers cannot currently install Access 2003 SP2. However, these customers may require a critical fix that is included in Access 2003 SP2. This critical fix is also included in the Access 2003 post-Service Pack 2 hotfix package that is described in this article, 902445. Because the Access 2003 post-Service Pack 2 hotfix package that is described in this article can be installed on computers that are running Microsoft Office Access 2003 Service Pack 1 (SP1), customers who cannot install Access 2003 SP2 can still obtain the critical fix if they install Access 2003 SP1 and then apply the Access 2003 post-Service Pack 2 hotfix package that is described in this article.

    Note When you apply the Access 2003 post-Service Pack 2 hotfix package that is described in this article, you may also experience the issue that is described in article 914830 in the Microsoft Knowledge Base.
  • When you try to update the data in tables that are linked to an Excel workbook in Microsoft Office Access 2003, you cannot edit, add, or delete data in the tables. For more information about this issue, click the following article number to view the article in the Microsoft Knowledge Base:
    904953 You cannot change, add, or delete data in tables that are linked to an Excel workbook in Office Access 2003 or in Access 2002

Properties

Article ID: 902445 - Last Review: November 15, 2007 - Revision: 3.4
APPLIES TO
  • Microsoft Office Access 2003
Keywords: 
kbautohotfix kboffice2003sp3fix kbsettings kbreport kbprogramming kbprint kbfunctions kberrmsg kbfix kbqfe kbhotfixrollup kboffice2003presp3fix kbhotfixserver KB902445

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com