Page 323 of 726« First...102030...321322323324325...330340350...Last »

After exporting Microsoft Dynamics CRM 2011 Dynamic Worksheets and/or Dynamic Pivot Tables using Claims Authentication, users do not see the expected data within the Excel worksheet

After exporting Microsoft Dynamics CRM 2011 Dynamic Worksheets and/or Dynamic Pivot Tables using Claims Authentication, users do not see the expected data within the Excel worksheet.

Users may see one of two things within the Excel Worksheet:
1. When using IFD Claims Authentication, users will see the ADFS sign-in page.
2. When using claims authentication, users will get a message stating:
“Script is disabled. Click Submit to continue”

Cause 1
Exporting the Dynamic Worksheet and/or Dynamic Pivot Table using Internet Explorer.

Cause 2
After export the Dynamic Worksheet and/or Dynamic Pivot Table using the Microsoft Dynamics CRM 2011 for Microsoft Office Outlook client, users did not refresh the data.

Resolution 1
Dynamic Worksheets and/or Dynamics Pivot Tables require the use of the Excel addin which is part of the Microsoft Dynamics CRM 2011 for Microsoft Office Outlook client. You must install the Microsoft Dynamics CRM 2011 for Microsoft Office Outlook found here:
http://www.microsoft.com/en-us/download/details.aspx?id=27821

(http://www.microsoft.com/en-us/download/details.aspx?id=27821)

Resolution 2
After exporting the Dynamic Worksheets and/or Dynamics Pivot Tables refresh the data.
a. Export the Dynamic Worksheets and/or Dynamics Pivot Tables from Microsoft Dynamics CRM 2011.
b. Open up the Dynamic Worksheets and/or Dynamics Pivot Tables with Excel.
c. Within Excel, click on Data tab.
d. Click on Refresh from CRM button.

You can workaround the requirement of using the Microsoft Dynamics CRM 2011 for Microsoft Office Outlook client by going through the following:
1.  Export the Dynamic Worksheets and/or Dynamics Pivot Tables from Microsoft Dynamics CRM 2011.
2.  Open up the Dynamic Worksheets and/or Dynamics Pivot Tables with Excel.
3. After the ADFS sign in page or the “Script is disabled” error shows in the worksheet, click on Data tab.
4. Click on Connections.
5. Within Workbook Connections, click on Properties.
6. Within Connection Properties, click on Definition tab.
7. Click on Edit Query button.
8.  Within the Edit Web Query, window you will need to do one of the following:
     - Using IFD Claims authentication, the Edit Web Query will redirect to ADFS login, enter in the user’s credentials and click on Sign In.
     - Using Claims authentication, continue to step 9.
9. After getting the Microsoft Dynamics CRM error, click on OK.
10. Within Edit Web Query, click on Cancel.
11. Within Connection Properties, click on Cancel.
12. Within Workbook Connections, click on Close.
13. Within Excel > Data tab, click on Refresh All.

Note: These steps are required every time you close and re-open the Dynamic Worksheets and/or Dynamics Pivot Tables.

Note This is a “FAST PUBLISH” article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use

(http://go.microsoft.com/fwlink/?LinkId=151500)

for other considerations.

Article ID: 2556284 – Last Review: July 19, 2012 – Revision: 3.0


Applies to
  • Microsoft Dynamics CRM 2011
kbmbsmigrate kbsurveynew KB2556284

Visit link:
After exporting Microsoft Dynamics CRM 2011 Dynamic Worksheets and/or Dynamic Pivot Tables using Claims Authentication, users do not see the expected data within the Excel worksheet

How To Use JScript or JavaScript to Traverse Through a Collection

This article describes how to use server-side scripts on Active Server Pages (ASP) pages with Visual Basic Script (VBScript) and JScript or JavaScript to traverse through a collection. In VBScript, you can use the FOR EACH…NEXT loop to traverse through a collection. In JScript or JavaScript, you must use an enumerator object.
The examples in this article use the file system object to traverse a folder (in this case, C:Text) and list all the files located in the folder. The first example uses a FOR EACH…NEXT loop in VBScript to traverse:

  1. Create a new folder in the root folder of drive C and name it “Text”.
  2. Place five text files in the directory you just created.
  3. Create a new ASP page and add the following VBScript code:
<% @LANGUAGE="VBScript" %>
<%
	'Reference the FileSystemObject
	set FSO = Server.CreateObject("Scripting.FileSystemObject")

	'Reference the Text directory
	set Folder = FSO.GetFolder("C:Text")

	'Reference the File collection of the Text directory
  	set FileCollection = Folder.Files

	Response.Write("VBScript Method
") 'Display the number of files within the Text directory Response.Write("Number of files found: " & FileCollection.Count & "
") 'Traverse through the FileCollection using the FOR EACH...NEXT loop For Each FileName in FileCollection strFileName = FileName.Name Response.Write(strFileName & "
") Next 'De-reference all the objects set FileCollection = Nothing set Folder = Nothing set FSO = Nothing %>

The following example demonstrates the equivalent but uses JScript or JavaScript and the enumerator object as shown below. Follow the steps outlined previously, except use the following code in step 3.

<% @LANGUAGE="JScript" %>
<%
	// Reference the FileSystemObject
	var FSO = Server.CreateObject("Scripting.FileSystemObject");

	// Reference the Text directory
	var Folder = FSO.GetFolder("c:Text");

	// Reference the File collection of the Text directory
  	var FileCollection = Folder.Files;

	Response.Write("JScript Method
"); // Display the number of files within the Text directory Response.Write("Number of files found: " + FileCollection.Count + "
"); // Traverse through the FileCollection using the FOR loop for(var objEnum = new Enumerator(FileCollection); !objEnum.atEnd(); objEnum.moveNext()) strFileName = objEnum.item(); Response.Write(strFileName + "
"); // Destroy and de-reference enumerator object delete objEnum; objEnum = null; // De-reference FileCollection and Folder object FileCollection = null; Folder = null; // Destroy and de-reference FileSystemObject delete FSO; FSO = null; %>

NOTE: The enumerator object is instantiated within the FOR loop, which is okay in JScript or JavaScript. The syntax for the FOR statement is as follows:

FOR(initialize ; test ; increment)
statement;

The output for each example in this article will appear differently. In VBScript, the output shows only the file name and its file extension as shown here:

VBScript Method
Number of files found: 5
test1.txt
test2.txt
test3.txt
test4.txt
test5.txt
					

In JScript or JavaScript, the output displays the physical folder, the file name, and its file extension:

JScript Method
Number of files found: 5
C:Texttest1.txt
C:Texttest2.txt
C:Texttest3.txt
C:Texttest4.txt
C:Texttest5.txt
					

The third-party products that are discussed in this article are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.

For more information on JScript and VBScript, please refer to the Microsoft Scripting

(http://technet.microsoft.com/library/ee176792.aspx)

Web site.

Article ID: 229693 – Last Review: July 19, 2012 – Revision: 3.0


Applies to
  • Microsoft Active Server Pages 4.0
  • Microsoft Internet Information Server 4.0
kbfso kbhowto kbscript KB229693

Continue reading here:
How To Use JScript or JavaScript to Traverse Through a Collection

OFFXP: Some Switches and Properties Are Ignored When Using the /j Switch

When you run Office Setup by using a command line that includes the /j switch (/jm or /ju), some command-line properties or switches are ignored. For example, some switches are ignored if you use the following command line to start Setup

pathSetup.exe /jm PackageName.msi companyname=”My Company” /le c:Officelog.txt

where path is the location of the installation point and PackageName.mst is the name of the Windows Installer .msi package
(for example, Proplus.msi).

When you first start an Office program a dialog box appears showing you user information. The Organization name box will not contain the company name you specified on the command line (for example, My Company). However, the Officelog.txt file will be created on the root of the C: drive.

NOTE: You will not see any notification that the switches or properties are being ignored.

When you run Setup using the /j switch, only a few command-line switches are applied during Setup. The following table lists the switches that are not ignored when you use the /j switch:

   Switch           Function
   -----------------------------------------------------------------------
   /wait            Setup.exe waits for Msiexec.exe to complete before
                    terminating.

   /settings        Used to specify an alternative file to the default
                    Setup.ini file.

   /l               Used to specify logging options. Must also include a
                    path to the log file.

   /q               Used to run Setup in Quiet mode.

   /autorun         Used to indicate that Windows runs Setup automatically
                    when you insert the Office CD into the CD-ROM or
                    DVD-ROM drive.
				
For a complete description of the command-line switches and properties for Office, see the following Microsoft Web site:

You can also download supplemental information (Orkdocs.exe) from the following Microsoft Web site:

After you download the Orkdocs.exe file, double-click it to extract the files. The Setupref.doc file comtains a complete list of the Setup command-line switches and properties.

Article ID: 297898 – Last Review: July 19, 2012 – Revision: 2.0


Applies to
  • Microsoft Office XP Professional Edition
  • Microsoft Office XP Small Business Edition
  • Microsoft Office XP Standard Edition
  • Microsoft Office XP Developer Edition
  • Microsoft Access 2002 Standard Edition
  • Microsoft Excel 2002 Standard Edition
  • Microsoft FrontPage 2002 Standard Edition
  • Microsoft Outlook 2002 Standard Edition
  • Microsoft PowerPoint 2002 Standard Edition
  • Microsoft Word 2002

Read the original:
OFFXP: Some Switches and Properties Are Ignored When Using the /j Switch

OFFXP: Running Setup with /ju Switch Advertises Office for All Users

When you run Office setup by using the /ju command-line switch, Office is advertised for any user who logs on to the computer rather than for the user running Setup.
When you use the /ju switch, the default setting passed to the Windows Installer is ALLUSERS=2. This will create a per-machine installation using folders in the All Users profile.
To work around this problem, use either of the following methods.

Method 1: Pass the ALLUSERS Property on the Command Line

Use this method to create a per-user installation. You cannot use this method in conjunction with the /ju switch. You will see the complete setup interface when you use this method.

To use the ALLUSERS property on the command line, follow these steps:

  1. Log on as a member of the Administrators group.
  2. On the Windows Start menu, click Run.
  3. In the Open box, type the following command line

    pathSetup.exe ALLUSERS=”"

    where path is the path to the installation point.

  4. Click OK.
  5. Choose your setup options in the Setup dialog boxes.
  6. If you are prompted to restart Windows after Setup has finished, click Yes.
  7. After the computer has restarted, log in as the same user.

Office will be installed with the options you chose. If you log off and then log back on as another user, you will not have access to the Office programs.

NOTE: If another member of the Administrators group follows this procedure after you installed Office by using the ALLUSERS=”" property, he/she will not be able to choose an install folder different from the folder you selected.

Method 2: Use a Transform that Includes the ALLUSERS Property

NOTE: If the Windows Desktop Update is not installed, use Method 1.

Use this method in conjunction with the /ju switch. You will not see any Setup interface with this method. If you have the Windows Desktop Update installed prior to running Setup, then this method installs Office as if you had chosen Installed on First Use for the entire Microsoft Office feature set.

NOTE: You cannot use the /ju switch and the ALLUSERS=”" property on the commmand line together because the /j switch will ignore most switches and properties that are also on the command line. However, this does not include the /t switch, which is why this method uses a transform.

To use a transform, follow these steps:

  1. Start the Custom Installation Wizard.
  2. Locate and select the Package Name.msi file where Package Name is the name of the Windows Installer .msi package (for example, Proplus.msi) and then click Next.

    NOTE: This file is typically located in the root folder of your Office installation source.

  3. In Step 3 of the wizard, select the Create a new MST file option, and click Next.
  4. In Step 4 of the wizard, type a path and file name for your transform file (.mst), and click Next.
  5. Proceed through the remaining steps of the wizard, setting any other options you want. In Step 21 of the wizard, in the Properties list, double-click ALLUSERS.
  6. In the Value list, click Clear property. Click OK.
  7. Click Finish.
  8. Note the command line provided in the last dialog box of the wizard. You will use a modified version of this to run setup.
  9. On the last page of the wizard, click Exit.
  10. As a member of the Administrators group, run setup using the following command line:

    pathSetup.exe /ju Package Name.msi /t path to transformtransform name.mst

  11. If you have the Windows Desktop Update installed, click any of the Office shortcuts on the Programs menu.
    The Windows Installer will start and finish the installation of the program you started.

NOTE: If you saved your transform in the same folder as package name.msi on your Office source location, then you do not have to specify a path to the transform in the above command line. Just provide the name of the transform after the /t switch.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
For more information about the Custom Installation Wizard, please see the following Microsoft Web site:

Article ID: 298031 – Last Review: July 19, 2012 – Revision: 3.0


Applies to
  • Microsoft Office XP Professional Edition
  • Microsoft Office XP Small Business Edition
  • Microsoft Office XP Standard Edition
  • Microsoft Office XP Developer Edition
  • Microsoft Access 2002 Standard Edition
  • Microsoft Excel 2002 Standard Edition
  • Microsoft FrontPage 2002 Standard Edition
  • Microsoft Outlook 2002 Standard Edition
  • Microsoft PowerPoint 2002 Standard Edition
  • Microsoft Word 2002

Read this article:
OFFXP: Running Setup with /ju Switch Advertises Office for All Users

OFFXP: Pros and Cons of "Run from Network" Installations

If you want to install Microsoft Office in a networked environment, you can
perform an administrative installation (Setup /a) of Microsoft Office.
After you perform an administrative installation, and Setup copies the
files to the network server, you and other users can perform the following
types of installations:
  • Run from My Computer
  • Run from Network
  • Installed on First Use

This article explains the advantages and disadvantages of performing a
“Run from Network” installation of Microsoft Office.

If you want to use the /a switch with Office XP, you need to obtain an Enterprise edition of Office.

For information about obtaining an Enterprise edition of Office XP, please visit the following Microsoft Web site:

Advantages

When you perform a workstation or a “Run from Network” server installation,
you can take advantage of the following benefits:

  • You can minimize the amount of hard disk space that is used on each computer. When you or other users perform this type of installation, the amount of disk space that Office requires is less than the amount that it requires when you perform either a “Run from My Computer” or “Installed on First Use” installation of Office. This is important if there is limited free hard disk space on your local computer.
  • Because program files are stored on a server, you can easily manage and maintain install options for multiple users. When installing an administrative install of Office you can selectively choose the install options for users by using the Custom Installation Wizard.

    For more information about the Custom Installation Wizard, see the Microsoft Office XP Resource Kit, available at the following Microsoft Web site:

Disadvantages

When you perform a “Run from Network” server installation, be aware of the following disadvantages:

  • When you perform an administrative installation of Office, more hard disk space is used on the server. The amount of disk space required on the server varies depending on the Office suite being installed.
  • When you perform a “Run from Network” installation, program performance may be slowed by high volumes of network traffic or by heavy use of the network server.
  • When you perform a “Run from Network” installation, you must be connected to the network server in order to run any of the Office programs. In addition, if the server is not operating (for example, for maintenance or repairs), you and other users cannot use the Office programs.

    If you have a laptop computer and you plan to use the computer outside of the Office, use the “Run from My Computer” installation option rather than the “Run from Network” installation option.

    NOTE: Although it may be possible to connect to your network by modem and remote network access, Microsoft recommends that you do not use this method to run Office. The amount of time that is required to download all of the files to run a single program will greatly hinder your productivity.

Article ID: 290358 – Last Review: July 19, 2012 – Revision: 2.0


Applies to
  • Microsoft Office XP Professional Edition
  • Microsoft Office XP Small Business Edition
  • Microsoft Office XP Standard Edition
  • Microsoft Office XP Developer Edition
  • Microsoft Access 2002 Standard Edition
  • Microsoft Excel 2002 Standard Edition
  • Microsoft FrontPage 2002 Standard Edition
  • Microsoft Outlook 2002 Standard Edition
  • Microsoft PowerPoint 2002 Standard Edition
  • Microsoft Word 2002

Visit site:
OFFXP: Pros and Cons of "Run from Network" Installations

OFFXP: UserName and CompanyName Fields Not Set to Blank

When you install Office, the UserName and CompanyName fields are filled in, even if you use a command-line switch or transform (.mst) file to suppress these fields.
This problem occurs when you attempt to set the UserName and CompanyName properties to blank, either by using a command line, or by specifying the settings in the Setup.ini file. For example, if you use the following command line to start Office Setup

setup.exe USERNAME=”" COMPANYNAME=”"

the UserName and CompanyName fields are still populated.

To set the UserName and CompanyName properties to blank, use the NoCompanyName and NoUserName properties. These properties can be used on the command line, in the Setup.ini file, or in a transform (.mst) file. When you use these properties, they must be set to one (1). For example, if you use the following command line to start Office Setup

setup.exe NOCOMPANYNAME=1 NOUSERNAME=1

the UserName and CompanyName fields will be suppressed.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
For additional information about how to customize Office Setup, refer to the Microsoft Office XP Resource Kit documentation, or browse to the following Microsoft Office XP Resource Kit Web site:

Article ID: 290167 – Last Review: July 19, 2012 – Revision: 2.0


Applies to
  • Microsoft Office XP Professional Edition
  • Microsoft Office XP Small Business Edition
  • Microsoft Office XP Standard Edition
  • Microsoft Office XP Developer Edition
  • Microsoft Access 2002 Standard Edition
  • Microsoft Excel 2002 Standard Edition
  • Microsoft FrontPage 2002 Standard Edition
  • Microsoft Outlook 2002 Standard Edition
  • Microsoft PowerPoint 2002 Standard Edition
  • Microsoft Word 2002

Continue Reading:
OFFXP: UserName and CompanyName Fields Not Set to Blank

OFFXP: Setup Quits When You Try to Install Office XP Directly from a Web URL Source

When you try to install Microsoft Office XP from a Web server by doing the following:
  1. You click the link to Setup.exe on the Web page that contains the administrative installation of Office.
  2. You click Run this program from its current location (or Open).

You cannot run Setup, and Setup may quit unexpectedly. As a result, you cannot install Office XP directly from a Web Uniform Resource Locator (URL) source.

This behavior may occur if you try to install Office XP from a secure Web server location. For example, user authentication or security (user name and password or HTTPS connection) is required to access the Web site.
To work around this problem, run Office XP Setup from the command line by using the /webinstall command-line option. To do this, follow these steps.

NOTE: Windows Installer requires that the Wininet.dll and Urlmon.dll files be installed on the client if you are installing from a Web server. This means that, to perform this procedure, you must use Microsoft Internet Explorer 3.0 or later.

  1. Start Internet Explorer and connect to the Web page that contains the administrative installation of Office XP. Type your user name and password (as appropriate) to access the page.
  2. Click the Setup.exe link.
  3. In the File Download dialog box, click Save this program to disk (or Save).
  4. In the Save in box, click Desktop, and then click Save.
  5. After the download is complete, click Start and then click Run.
  6. In the Open box, type the appropriate line where local path is the location on the local hard disk where you saved the Setup.exe file, domain is the domain name, user name is your user name, password is your password, and administrative installation folder is the folder on the Web server that contains the Office XP installation files. Click OK.

    local pathsetup.exe /webinstall “http://domain%5Cuser name:password@server name/administrative installation folder

    -or-

    local pathsetup.exe /webinstall “https://domain%5Cuser name:password@server name/administrative installation folder

    NOTE: Do not include “http://” or “https://” in the server name parameter. Also, if you do not have a domain, specify user name:password in the command line. If you have a domain, you cannot type a backslash character () in the command line. Instead, you must type %5C after the domain name.

  7. Follow the steps in the Office XP Setup Wizard to install Office XP.NOTE: Microsoft does not recommend that you perform an HTTP installation of Office XP from a Web server under certain scenarios.

    For additional information about this recommendation, click the article number below
    to view the article in the Microsoft Knowledge Base:

    328748

    (http://support.microsoft.com/kb/328748/EN-US/
    )

    OFFXP: Microsoft Does Not Recommend Installing Office XP from a Web Server

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
For more information, view the “Installing Office from a Web Server” section of the Microsoft Office XP Resource Kit. To do so, visit the following Microsoft Web site:

For more information about how to deploy Office XP, see the Microsoft Office XP Resource Kit. To do so, visit the following Microsoft Web site:

For additional information about Setup command-line options for Office XP, click the article number below
to view the article in the Microsoft Knowledge Base:

283686

(http://support.microsoft.com/kb/283686/EN-US/
)

OFFXP: Setup Command-Line Switches for Office XP

Article ID: 280669 – Last Review: July 19, 2012 – Revision: 2.0


Applies to
  • Microsoft Office XP Professional Edition
  • Microsoft Office XP Small Business Edition
  • Microsoft Office XP Standard Edition
  • Microsoft Office XP Developer Edition
  • Microsoft Access 2002 Standard Edition
  • Microsoft Excel 2002 Standard Edition
  • Microsoft FrontPage 2002 Standard Edition
  • Microsoft Outlook 2002 Standard Edition
  • Microsoft PowerPoint 2002 Standard Edition
  • Microsoft Word 2002

View article:
OFFXP: Setup Quits When You Try to Install Office XP Directly from a Web URL Source

OFFXP: Office Resource Kit Does Not Contain Operating System Policy Templates

When you use the System Policy Editor that is installed by the Microsoft Office XP Resource Kit (ORK), you may not see any policy settings that relate specifically to the operating sytem.
When you install the ORK, the following three System Policy templates are not installed:

  • Winnt.adm
  • Windows.adm
  • Common.adm
The three templates listed in the “Cause” section are available with either the Microsoft Windows 98 Resource Kit, or the Microsoft Windows NT 4.0 Resource Kit.

For more information about the Microsoft Office XP Resource Kit (ORK), please browse to the following Microsoft Web site:

Article ID: 290299 – Last Review: July 19, 2012 – Revision: 2.0


Applies to
  • Microsoft Office XP Professional Edition
  • Microsoft Office XP Small Business Edition
  • Microsoft Office XP Standard Edition
  • Microsoft Office XP Developer Edition
  • Microsoft Access 2002 Standard Edition
  • Microsoft Excel 2002 Standard Edition
  • Microsoft FrontPage 2002 Standard Edition
  • Microsoft Outlook 2002 Standard Edition
  • Microsoft PowerPoint 2002 Standard Edition
  • Microsoft Word 2002

View original post here:
OFFXP: Office Resource Kit Does Not Contain Operating System Policy Templates

Project Web access tab is blank when you double-click a Project Server 2003 Outlook calendar item

When you double-click a Microsoft Office Project Server 2003
Outlook calendar item, the Project Web access tab is blank
instead of displaying the timesheet.
This problem occurs when Microsoft Outlook is installed on a
Terminal Server system if the Outlook Visual Basic Scripting Support is not
installed.

Temporarily Disable Terminal Services

To do this, follow these steps:

  1. Click Start, right-click My
    Computer
    , and then click Manage.
  2. Expand Services and Applications, click
    Services, right-click Terminal Services, and
    then click Properties.
  3. In the Startup Type box, click
    Disabled.

    Note Make a note if the current setting is Manual or Automatic so that
    you can restore this setting later.

Install the Scripting Support

  1. To download Microsoft Windows Script 5.7 for Microsoft Windows 2000 and Microsoft Windows XP, visit the following Microsoft Web site:
  2. Click Download, and then click Run
    this file from current location
    .

    For additional information about how to download
    Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:

    119591

    (http://support.microsoft.com/kb/119591/
    )

    How
    to obtain Microsoft Support files from Online Services

    Microsoft scanned this file for viruses.
    Microsoft used the most current virus-detection software that was available on
    the date that the file was posted. The file is stored on security-enhanced
    servers that help to prevent any unauthorized changes to the file.

Enable Terminal Services Again

  1. Click Start, right-click My
    Computer
    , and then click Manage.
  2. Expand Services and Applications, click
    Services, right-click Terminal Services, and
    then click Properties.
  3. In the Startup Type box, click
    Automatic or click Manual.

Article ID: 827401 – Last Review: July 19, 2012 – Revision: 4.0


Applies to
  • Microsoft Office Professional Edition 2003
  • Microsoft Office Outlook 2003
  • Microsoft Office PowerPoint 2003
  • Microsoft Office Publisher 2003
  • Microsoft Office Small Business Edition 2003
  • Microsoft Office Basic Edition 2003
  • Microsoft Office Access 2003
kbremoting kbsetup kbprb KB827401

Read the original post:
Project Web access tab is blank when you double-click a Project Server 2003 Outlook calendar item

Description of the Access 2003 post-Service Pack 1 hotfix package: January 19, 2005

Microsoft has released the Access 2003 post-Service Pack 1 hotfix package for Microsoft Office Access 2003. This article describes the following items about the hotfix package:

  • Issues that the hotfix package fixes
  • 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 to use one or more of the hotfixes in the package
  • The files that the hotfix package contains
This article describes the Microsoft Office Access 2003 issue that is fixed in the Access 2003 post-Service Pack 1 hotfix package that is dated January 19, 2005.

Issues that the hotfix package fixes

This hotfix package fixes the following issue that was not previously documented in a Microsoft Knowledge Base article:

  • You run a Microsoft Visual Basic for Applications macro that uses the TransferDatabase action to link many database tables from an Access database (.mdb file) or an Access project (.adp file) to another Access database. When you do this, one or more of the following conditions may occur:
    • Available memory that is used during the running of the macro is not released when the macro has completed.

      To view the available memory in Windows, press CTRL+ALT+DEL, click Task Manager, and then click the Performance tab.

    • Access 2003 may appear to stop responding.
    • When you try to quit Access 2003, Access may take approximately five minutes to quit after you run the macro.
    • You receive the following error message:

      Microsoft Office Access has encountered a problem and needs to close. We are sorry for the inconvenience.

Service pack information

This problem was first corrected in Office 2003 Service Pack 2.

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

(http://support.microsoft.com/kb/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:

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-Office 2003 Service Pack 1 (SP1) hotfix. To install the hotfix, you must have Microsoft Office 2003 SP1 installed.

    For additional information about Office 2003 SP1, click the following article number to view the article in the Microsoft Knowledge Base:

    842532

    (http://support.microsoft.com/kb/842532/
    )

    Description of Office 2003 Service Pack 1

  • 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 Office 2003 SP1 installed or on a computer that is running Office 2003 without Office 2003 SP1 installed. However, we have tested this hotfix more extensively on a computer that is running Office 2003 with Office 2003 SP1 installed than we have on a computer that is running Office 2003 without Office 2003 SP1 installed. If you install this hotfix on a computer that is running Office 2003 without Office 2003 SP1 installed, 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 or to modify any registry keys to enable the hotfix that this package contains.

Hotfix file information

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

The global version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it 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
   Date         Time   Version        Size       File name
   -------------------------------------------------------------------------
   19-Jan-2005  22:25  5.0.2919.6304  3,422,240  Office2003-kb892470-glb.exe

Microsoft Windows Installer .msp file information
   Date         Time   Size       File name
   ------------------------------------------------------------------------
   19-Jan-2005  21:44  4,739,072  Msaccessff.msp (full-file/administrative)
   19-Jan-2005  21:00  1,324,544  Msaccessop.msp (optimized)

After the hotfix is installed, the global version of this hotfix has the file attributes (or later file attributes) that are listed in the following table:

   Date         Time   Version      Size       File name
   --------------------------------------------------------
   18-Jan-2005  21:42  11.0.6418.0  6,634,184  Msaccess.exe

Additional notes:

  • For additional information about how to install this hotfix, see the Readme.txt file that is included in the hotfix package.
  • For additional 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:

For additional information about the terminology that Microsoft uses when it corrects software after it is released, click the following article number to view the article in the Microsoft Knowledge Base:

824684

(http://support.microsoft.com/kb/824684/
)

Description of the standard terminology that is used to describe Microsoft software updates

Article ID: 892470 – Last Review: July 19, 2012 – Revision: 5.1


Applies to
  • Microsoft Office Access 2003
kbautohotfix kbqfe kbhotfixserver kboffice2003sp2fix kberrmsg kbvba kbprogramming kbbug kbfix kbhotfixrollup kboffice2003presp2fix KB892470

Continued here:
Description of the Access 2003 post-Service Pack 1 hotfix package: January 19, 2005

Page 323 of 726« First...102030...321322323324325...330340350...Last »

Recent Comments

    Archives

    Categories