Could someone explain to me why the United States spends more money killing people than taking care of its own?
The tax rebate is Bush and his cronies way of bailing out big corporations using tax payers' money, it is NOT to help poorer America.
Why is there money to help big corporations, killing people, but when it comes to Social Security, the money is running out? Why don't they bail out Social Security? My measly $300 rebate has already gone to Big Oil. Yours most likely will end up in some big corporation's pockets too and our children will have to pick up the tab.

Gal 3:26   For ye are all the children of God by faith in Christ Jesus.

Another great site for Office Support and Help is

Rick Selby's
Office 2002-03

Site Visitors 
To find a topic on this page, Click Edit on the Toolbar, Find (on this page), type in keyword

Need Help, click here for support.

If you are planning on upgrading to Vista, there are hardly any drivers available. They are not the same as XP and most likely you will not be able to find drivers for your hardware at this time. Check with your manufacture for Vista drivers before you upgrade or you may be out of luck for a while until someone comes up with drivers. This is another repeat of XP SP 2.

Three things to remember when you are working with computers.
• First thing is "YOU CAN DO IT".
• Second take your time, a little mistake can cause a big problem.
• Third all answers are only a question away.
Three things to remember when you are working with computers.
• First thing is "YOU CAN DO IT".
• Second take your time, a little mistake can cause a big problem.
• Third all answers are only a question away.

Important Message!!!
Most problems with XP such as Error Messages, vxd Problems, Fatal Exceptions and other errors are the same as earlier Window Operating Systems. If you don't find the answer to a certain problem on this page please check the Windows Page and the Troubleshooting Page.

TABLE OF CONTENTS is after these links.
Here are some links for online virus program and also free spyware programs.
If you are experiencing computer Problems such as slowness, strange icons appearing, tool bars appearing, home page changing, please use one of the following links to check for a virus or trojan.

If your computer has System Restore make sure you disable it before running any of these programs.
Remember to Enable System Restore once you have finished.
• Panda Virus Free Online Virus Scan
  
• Trend Micro Free Online Virus Scan
  
• AVG Anti-virus Program (FREE)
  • AVG is a great "FREE" program and I used to keep a link to the download but they keep changing it all the time and I can't keep this link up to date so Google "Download AVG Free" to get the download link. SORRY!

If your computer has System Restore make sure you disable it before running any of these programs.
Remember to Enable System Restore once you have finished.
• Spyware Guide
  • A free online scan for cleaning Spyware and Adware.  Click Here to Run Scan
• Ad-aware Should be run in Safe Mode
  • A great program for cleaning Spyware
  • Download Here
• CW Shredder Should be run in Safe Mode
  • A program for cleaning Cool Web Search variants.
  • Download Here
• Hijacked this Cannot be run in Safe Mode
  • Download Here


TABLE OF CONTENTS

Basically MS Word 97, 2000, XP, 03 and 07 are the same. Where they differ most is in the menus and the newer versions have more features. The basic operations of all are almost the same. The instructions listed on these pages are just basic instructions. The toolbars differ a little but the functions most people use daily are the same.

Office 2007 Fromat not compatiable with earliers versions.
When a file is created in MS Office 07 and saved in 07 format the earlier version cannot open, edit and save the formatting. 07 has features and formatting that the earlier versions do not recognize. Microsoft has a conversion tool out you can download to make 07 fromat work with the earlier versions of MS Word so they can open, edit and save in the 07 format.

Download the convertion tool here but make sure you have all the Office Updates installed first.

IF you are looking for basic instructions for the use of the Office XP and 03 Programs use the Links Buttons to the various Web Pages for MS Word, MS Excel, MS Access, MS Forms, ... listed above.

This page is for Solving Problems with Office 2002 and 03. If you are looking for help using features in the Office Suite try the pages for Access Tables, Access Reports, Access Queries, Access Forms, Excel, and Word. They have the instructions on how to use the "Major" features, not all but most features of these programs.

This is a tough page to list errors so they are easy to find. Some error messages pertains to all Office Programs where others pertain to a certain program such as Excel.
If a problem pertains to all Office programs it will be listed under the heading pertaining to the problem. If it pertains to just one of the Office programs then it will be listed under the Program or maybe even both ways.

Errors In MS Office Caused by Vista
• "The Office Assistant requires Microsoft Agent 2.0 or later"
• When you start Word 2002 from Works Suite 2006 on a Windows Vista-based computer: "Error 1706. No valid source could be found"
• When you try to install Word 2002 template wizards from Works Suite 2006 on a Windows Vista-based computer: "Error 1706. No valid source could be found"
Access Errors
• You Receive A "The Application Failed To Initialize Properly (0xc0150002)" Error Message When You Start An Office 2003 Program On A Windows XP Professional-Based Computer
• Office 2003 cannot run in "Windows 98/Windows Me" compatibility mode
• "Microsoft Access can't find the wizard" Error Message When You Use Wizards in Access 2003
Excel-Word E-mail Errors
• You Receive A "The Application Failed To Initialize Properly (0xc0150002)" Error Message When You Start An Office 2003 Program On A Windows XP Professional-Based Computer
• "Excel Could Not Start The E-Mail Program" Error Message When You Use The Send To Command In Excel 2002
Entering Data Errors
• Run-Time Error '1004': Programmatic Access to the Visual Basic Project
• "This Page Has Been Saved To A Web Server That Is Not Configured To Allow Connections To The Datasource"
• "Could Not Find File"
• "The Microsoft Jet Database Engine Cannot Open the File ''. It is Already Opened Exclusively by Another User, or You Need Permissions to View It's Data"
• "The Use RemoteProvider Property is Supported Only For Pages Saved to Web Folders"
• "Safety Settings On This Computer Prohibit Accessing A Data Source On Another Domain"
• "Could Not Use "; File Already In Use"
• "Cannot Start Your Application. The Workgroup Information File Is Missing Or Opened Exclusively By Another User"
Excel Errors
• Smart Tags listed below under "Smart Tags"
• You Receive A "The Application Failed To Initialize Properly (0xc0150002)" Error Message When You Start An Office 2003 Program On A Windows XP Professional-Based Computer
• Repairing corrupted files in Excel
• Excel opens without displaying a workbook
• Office 2003 cannot run in "Windows 98/Windows Me" compatibility mode
• Cannot Empty Clipboard Error Message
• "Run-time Error 1004: Application or Object-Defined Error" Error Message When You Make Changes to the Excel Chart Legend
• Error Checking Is Not Available When Worksheet Is Protected Or Workbook Is Shared In Excel
• Cannot Remove Error Tracing Arrow in Excel
• You Receive A "The Document Caused A Serious Error The Last Time It Was Opened" Error Message When You Open A Word 2003 Or Excel 2003 Document
FrontPage

• You receive a "Documents in this folder are not available" error message when you try to open a Web folder in Internet Explorer
• HTML Is Reformatted When Component Properties Are Modified In Html View In FrontPage
• "Unable To Retrieve Folder Information From The Server" Error Message When You Try To Run An Executable In A Root Folder
• ASP Error 0178: 80070005 When You Attempt To Connect To Database Results Page
• Error Message Appears Editing Web Page On A Sharepoint Portal Server
• "Error Removing One Or More Users" When Adding User As A Browser On An Apache Server
• Database Error Messages When You Disable Session State In FrontPage 2002 Server Extensions From Microsoft
• Web Sites Do Not Open In Microsoft FrontPage After You Configure FrontPage Server Extensions 2002 On An Apache 1.3.19 Or Later Web Site
• Web Clients Receive "Cannot Run The FrontPage Server Extensions On This Page" Error Message When They Submit A Feedback Form
• "Fatal Exception 0e" Error Message During FrontPage Installation
• You Receive An Error Message When You Click Next In A Paged Data View In FrontPage 2003
• You Receive An Error Message When You Try To Start FrontPage 2003 For a Microsoft FrontPage 2002 and FrontPage 2000 version of this article, see 321486 in the Microsoft Knowledge Base
• Error Message: Database Results Error [Microsoft][ODBC SQL Server Driver][Named Pipes]Access Denied
• "The Folder '/' Is Marked Executable" Error Message When You Save A Page To A Folder On A Web Site Based On Iis In FrontPage 2002 & 03
• "Server error: Cannot close file /_vti_pvt/service.cnf" error message when you try to publish Web in FrontPage
• Portal site stops responding and you receive a "The page cannot be displayed" or "Cannot find server or DNS error" error message when you access a portal site in SharePoint Portal Server 2003
• You receive a "You are not authorized to view this page" error message when you click Help on a single sign-on administration page in SharePoint Portal Server 2003
• You receive a "The virtual server referenced here is not in the config database" error message when you unextend a virtual server in SharePoint Portal Server 2003
Import Errors
• Fields Are Not Mapped Correctly When You Use The Import Text Wizard To Import A Comma-Delimited Text File
• You Receive An Error Message When Importing, Exporting Or Linking Text Files
• Skipped Fields Are Imported When You Import Data From A Comma-Delimited Text File To An Existing Table
• Column Format On A Microsoft Excel Worksheet Is Lost Or Changed When You Import Or Link Data From Excel
• Unexpected Error From External Database Driver (8961)" Error Message When You Try To Import Dbase Files Into Access
Initialing Office Suite Errors
• "Error 1304: Error Writing to the File" When You Install Office XP-03 or Office 2000
• Error 1311 - Source file not found: D:\OFFICE1.CAB ...
• Error 1335 - Error 1335-Cannot copy cab file Office1.cab
• Office Setup Does Not Complete Because BackWeb Agent Is Running
Links Errors
• Hyperlinks in Embedded Excel Workbook Do Not Work
Machine Debug Manager (MDM)
• Turn Off Machine Debug Manager In Office XP
Opening Program, Tables, Reports... Errors
• You Receive A "The Application Failed To Initialize Properly (0xc0150002)" Error Message When You Start An Office 2003 Program On A Windows XP Professional-Based Computer
• Office 2003 cannot run in "Windows 98/Windows Me" compatibility mode
• The Document Caused a Serious Error the Last Time it Was Opened
• A Collation Conflict Error Occurs When You Open An Access Project Table Or View
• Error 800A175D - Could Not Open Macro Storage
Outlook 2002 Errors
• You Receive An Error Message When You Open An E-Mail Message That You Saved With Outlook 2003
  • The messaging interface has returned an unknown error. If the problem persists, restart Outlook
• "Norton Antivirus 2005 Does Not Support The Repair Feature. Please Uninstall And Reinstall."
• Second Hotmail Account In Outlook
Outlook 2003 Errors
• You Receive An Error Message When You Open An E-Mail Message That You Saved With Outlook 2003
  • The messaging interface has returned an unknown error. If the problem persists, restart Outlook
• "Cannot start Microsoft Outlook" error message when you start Outlook 2003
• Error message: "The Data File 'Personal Folders' Was Not Closed Properly. Checking For Errors."
• "Norton Antivirus 2005 Does Not Support The Repair Feature. Please Uninstall And Reinstall."
• Second Hotmail Account In Outlook
• E-mail messages do not appear when you add a second Hotmail account in Outlook 2003
• Smart Tags Do Not Appear In Outlook 2003 After You Install Windows XP SP2
• You Receive an Error Message When You Start Outlook 2003 The file drive:\path\file name.pst could not be found
• You Receive an Error Message When You Start Outlook 2003 A recently installed program may cause
• "Cannot Start Microsoft Outlook" Error Message When You Start Outlook After Custom Installation Wizard
• Outlook 2003 stops responding, and you receive "Riched20.dll" error messages when you start Outlook 2003
• You Cannot Use the /select Switch to Start Outlook 2003
Password and Identity Problems
• ' reported error (0x80040154') : 'Internet Mail is not registered properly. Please reinstall and try again.'' 454 5.7.3 Client Does Not Have Permission To Submit Mail To This Server
• You Are Repeatedly Prompted for Credentials When You Log On to Your Mail Server
• Outlook Express and Outlook Repeatedly Prompt You for Your Password
• Outlook Express Does Not Prompt You for an Identity
Save Errors
• Error Message When You Try to Save Presentation, Workbook, or Document
Setup / Install Errors
• "Installation Error: File not Found
  A required installation file SKU011.CAB could not be found
• "Installation Error: File not Found
  A required installation file file_name.CAB could not be found.
• "Original Installation Source Required:
• "If you installed the program name from a CD, insert your CD. If you installed the program name over your computer network, locate the installation source on your network. Once you have located your installation source, click OK.
• "Error 1304: Error Writing to the File" When You Install Office XP-03 or Office 2000
• Office 2003 cannot run in "Windows 98/Windows Me" compatibility mode
• Cannot Install the Necessary Files Due to Windows Installer Error 1605" Error Message When You Try to Start Word
• "Error 1919. Error Configuring ODBC Data Source" Error Messages When You Run Setup for Office 2003
Smart Tags
• Smart Tag Indicators Do Not Appear or Work as Expected in Your Document
• Smart Tag Indicators Don't Appear in Document After You Turn on Smart Tags
• Smart Tags Do Not Appear In Outlook 2003 After You Install Windows XP SP2
Windows Picture and Fax Viewer Errors
• "No Preview Available" and "File Format Is Not Supported" Error Messages Occur When You Try to View Graphic Files
MS Word Errors
• Smart Tags listed above under "Smart Tags"
• You Receive A "The Application Failed To Initialize Properly (0xc0150002)" Error Message When You Start An Office 2003 Program On A Windows XP Professional-Based Computer
• Office 2003 cannot run in "Windows 98/Windows Me" compatibility mode
• Corrupt Normal.dot Causes Errors When Automating Word
• You Receive A "The Document Caused A Serious Error The Last Time It Was Opened" Error Message When You Open A Word 2003 Or Excel 2003 Document
• Error Message: Microsoft Word Has Encountered a Problem and Needs to Close
• Cannot Install the Necessary Files Due to Windows Installer Error 1605" Error Message When You Try to Start Word
• Reference Source Not Found" Error Message When You Change Numbering Formats For A Caption In Word 2003
• Document Actions Task Pane Disappears And You Receive An "Internal Error" Error Message When You Merge Two Office Solution Accelerator For Proposals Documents
• Error 800A175D - Could Not Open Macro Storage
• "Run-time Error '5663': Microsoft Mail Local Fax is Not Installed on Your System" When You Send a Fax in Word 2003
• "MS Visual C++ Runtime Library Runtime Error!" Error Message When You Try to Quit Word or Close a Word Document
• You Receive A "Microsoft Word Has Encountered A Problem And Needs To Close" Error Message When You Try To Start Word 2002 Or Word 2003
• "Word Was Not Able To Open The Data Source" Error Message When You Try To Insert A Selection Of Database Records Into A Word 2003 Document
• You Receive An Error Message When You Try To Close Or Save A Word 2003 Document
• You Receive Error Messages When You Start Word 2003

"Microsoft Access can't find the wizard" Error Message When You use Wizards in Access 2003
Error
• When you try to start a wizard in Microsoft Office Access 2003, such as the Link Table wizard, the Import Text wizard, or the Form wizard, the wizards may not start successfully, and you may receive the following error message
  Microsoft Access can't find the wizard or there is an incorrect setting in the windows registry.
Solution
• To resolve this problem, you must obtain the latest Jet 4.0 service pack that contains an updated version of the Jet 4.0 database engine
• For additional information about how to obtain the latest version of the Jet 4.0 database engine, read the following article number in the Microsoft Knowledge Base
  239114 How To: Obtain the latest service pack for the Microsoft Jet 4.0 database engine

Cannot Empty Clipboard Error Message
Excel 2000, 2002, 2003
This completely clears the contents of Windows Clipboard for all
Error Message
Cannot empty clipboard error message
• If you are receiving low memory errors this is a good way to free up some memory space. This will clears ALL clipboard contents.
Solution
• Select and copy above code (Ctrl + C)
  Option Explicit
  Public Declare Function OpenClipboard Lib "user32" (ByVal hwnd As Long) As Long
  Public Declare Function EmptyClipboard Lib "user32" () As Long
  Public Declare Function CloseClipboard Lib "user32" () As Long
  
  Public Function ClearClipboard()
  
  OpenClipboard (0&)
  EmptyClipboard
  CloseClipboard
  End Function
  
  Sub ccc()
  
  Call ClearClipboard
  End Sub
• In Excel open the Visual Basic Editor (VBE) with Alt + F11
• Select any file on left, choose Insert-Module from the menu
• Paste code in right pane Ctrl + V
• Close the VBE with Alt + Q
• Test the code:
  • In Excel run macro 'ccc' by pressing Alt+F8

Run-Time Error '1004': Programmatic Access to the Visual Basic Project
Error
• When you run code that uses the Microsoft Visual Basic for Applications Extensibility 5.3 Library, you may receive the following error message:
  Run-time error '1004': Programmatic access to the Visual Basic Project is not trusted
Cause
• Microsoft Excel 2003 contains a security feature that allows you to choose whether programmatic access to the Visual Basic project is trusted
• The default setting is to not trust programmatic access to the Visual Basic project
Solution
• On the Tools menu, point to Macro, and then click Security
• In the Security dialog box, click the Trusted Sources tab
• Select the Trust access to Visual Basic Project check box
• Click OK

"Run-time Error '3709'" error Message When You Enter A Large Amount Of Text In A Memo Field That Contains An Index
Error Message
• When you create a Memo field in a Microsoft Access database and create an index on that field (or you create a field name that includes text that is automatically indexed), you can enter only a specific amount of text. Once you reach this limit (approximately 3450 characters), you can enter no more text and you can also not edit the existing data. If you try to do so, you receive the following error message:
  Run-time error '3709':
  
  The search key not found in any record.
Solution
• Delete the index for the Memo field
  • Open the table with the Memo field in Design view
  • On the View Menu
  • Click Indexes
  • Click the index for the Memo field, and then delete it
Steps to Reproduce the Behavior
• In a new database, create a new table with the following properties, and then save it as Table1:
  Table: Table1
  ------------------------
  Field Name: Id
  Data Type:   AutoNumber
  Primary Key
  
  Field Name:   MyCode
  Data Type:   Memo
• Add the following record to the Table1 table:
  Id            MyCode
  ------------------------------------
  1            This is the Memo test data
  
  
• Copy the following SQL statement, paste it into a new query in SQL view, and then save the query as query1:
  UPDATE Table1 SET Table1.MyCode = [MyCode] & " " & [MyCode];
• Create the following module, and then save it Module1:
  Sub TestMemoUpdate()
  Dim i As Integer
  Docmd.setwarnings false
  For  i  =  1  To  10 Docmd.openquery "Query1"
  Next  i
  Docmd.setwarnings true
  End Sub
• Place your pointer so that it is in the procedure. Press F5 to run the code.

"This Page Has Been Saved To A Web Server That Is Not Configured To Allow Connections To The Datasource"
• This error is typically associated with the msdfmap.ini file on the Web server.
• The following steps allow any connection through RDS to data sources on the Web server.
• Use these steps for troubleshooting only.
  • On the Web server, open the msdfmap.ini file in WordPad. This file is in the WINNT folder
  • In the "[connect default]" section, change
    Access=NoAccess
  • To read
    Access=ReadWrite
  • Important: This will allow read/write connections to all data connections on the server through RDS
  • To read: In the [sql default] section, change
    SQL=" "
  • To read
    ;SQL=" "
  • Important: This allows any SQL statement to be executed against any data source on the Web server through RDS
  • To read: Save and close the msdfmap.ini file

"Could Not Find File"
• These errors include the following messages:
  • Could not find file " ".
  • Not a valid file name.
  • Microsoft Office Web Components could not open the database " ".
• Note: Before you receive these error messages, you may first receive the following error message:
  Data provider could not be initialized.
  These errors occur when the database cannot be found because of a data source that is not valid in the ConnectionString for the page, or when the UseRemoteProvider property is not configured properly.
• For additional information about valid connection strings for data access pages, read the article number below on the Microsoft Knowledge Base
  304324 HOW TO: Change the connection string for an Access 2002 data access page
• For additional information about which OLE DB providers can be used with data access pages, read the article number below on the Microsoft Knowledge Base
  304521 ACC2002: Supported providers for data access pages
• When you set the UseRemoteProvider property to False, the data access page checks on the local computer for the data source.
• When you set the UseRemoteProvider property to True, the data access page checks the Web server for the data source. This is known as three-tier data access.
• To configure the UseRemoteProvider property, follow these steps:
  Start Microsoft Access
  • Open the data access page that you are deploying in Design view
  • On the View menu
  • Click Properties to view the property sheet if it is not already visible
  • On the Edit menu, click Select Page to view the properties for the page
  • On the Data tab, set the UseRemoteProvider property to True Close and then save the data access page
  • Important: As soon as you set the UseRemoteProvider property to True, data can no longer be viewed when the page is opened from the file system.
  • Do not set the property until you are ready to publish the page from a properly configured IIS Web server.

"The Microsoft Jet Database Engine Cannot Open the File ''. It is Already Opened Exclusively by Another User, or You Need Permissions to View It's Data"
• This error is typically caused when there are not enough file system permissions for either the folder in which the database resides, or for the database file itself.
• Users accessing your pages must have at least read, write, create, and delete permissions to work with the .ldb file that is created by the Microsoft Jet database engine.
• For additional information about .ldb files, read the article number below on the Microsoft Knowledge Base:
  299373 ACC2002: Introduction to .ldb Files
• You may also receive this error if the database is opened exclusively by another user.
• Note:This error does not occur with pages that are bound to SQL Server objects.

"The UseRemoteProvider Property is Supported Only For Pages Saved to Web Folders"
You receive this error when you open a data access page from a file system location after the UseRemoteProvider property has been set to True
• When the UseRemoteProvider property is set to True, you must access the page through an Internet protocol such as HTTP.
• For example, if the page is stored in the wwwroot directory on the Web server, you access it as follows:
  http://ServerName/PageName.htm

"Safety Settings On This Computer Prohibit Accessing A Data Source On Another Domain"
• This error is caused by cross-domain settings on the local computer and occurs when accessing data across domains is not allowed.
• Note: that "domain" refers to Internet/Intranet domain, and not to network domain.

"Could Not Use "; File Already In Use"
• You receive this error when the database is opened exclusively by another user.
• This is common when browsing to a data access page after you create a new database.
• Close the database, and then refresh the page to remove the error.

"Cannot Start Your Application. The Workgroup Information File Is Missing Or Opened Exclusively By Another User"
• This error message occurs when a data access page cannot find the workgroup information file (.mdw).
• When you are using two-tier deployment, make sure that you put the workgroup file in a shared folder along with the database.
• Change the connection on the page to use the UNC path to the workgroup file as follows:
  • Start Microsoft Access
  • Open the data access page that you are deploying in Design view Right-click the page
  • Click Page Properties
  • On the Data tab, click the Build (...) button to the right of the ConnectionString property
  • On the All tab, change the Jet OLEDB:System database property to the UNC location for the workgroup file
• When you are using three-tier deployment, put the workgroup file with the database and make sure that the Jet OLEDB:System database property points to the correct path of the .mdw file

Repairing corrupted files in Excel
• Open Excel 2002 or 03
  • On the File menu, click Open
  • In the Open dialog box, select the file you want to open
  • Click the arrow next to the Open button
  • Click Open and Repair
  • Choose which method you want to use to recover your workbook
    • If You Can Open The File In Excel
      Revert To Saved Document command
      • If you are editing a Microsoft Excel worksheet and the file becomes corrupted before you have saved changes to the file, you can recover the original worksheet by doing the following:
        • On the File menu, click Open
        • select the name of the file that you are editing
          A dialog box appears with the message "Revert to Saved Document?"
        • Click OK
        • The file you are editing reverts to the last saved version of the file
      Save the file in SYLK format
      • Saving the file in SYLK format is typically used to remove printer corruption.
      • If you can open the corrupted Microsoft Excel file, you can "filter" it if you save it in SYLK format
      • Close the file
      • Reopen it using the following instructions
        • On the File menu, click Save As
        • In the Save as type list, click SYLK (Symbolic Link)
        • Click Save
        • Note: Only the active sheet in the workbook is saved when you use the SYLK file format.
          • Click OK when the message tells you the selected file type does not support workbooks.
          • Click Yes when the message tells you the file may contain features that aren't compatible with the SYLK format
        • On the File menu, click Close
        • On the File menu, click Open
        • Select the .slk file you saved
        • Click Open
        • Note: The .slk file may not be visible and you may need to click All Files in the Files of type list
        • On the File menu, click Save As
        • In the Save as type box, click Microsoft Excel Workbook
        • Click Save
        • Note: Because this format saves only the active worksheet, you must open the corrupted file repeatedly and save each worksheet separately
      Save the file in Hypertext Markup Language (HTML) format
      • If you can open the corrupted Microsoft Excel file, you can "filter" it if you save it in HTML format
        • Close the file
        • Reopen it using the following instructions
        • On the File menu, click Save As
        • In the Save as type list, click Web Page (*.htm, *.html)
        • Under Save
        • Click Entire Workbook
        • Click Save
        • Close the file
        • Open the file again in Excel
        • On the File menu, click Save As
        • In the Save as type list, click Microsoft Excel Workbook
        • Change the name of the file to create a new "filtered" copy without replacing the original
        • Note: Some features may be lost when you save in HTML format
    • If You Can't Open The File In Excel
      Set the recalculation option in Excel to manual
      • Start Excel
      • Open a blank workbook if one is not open on the screen
      • On the Tools menu, click Options
      • Click the Calculation tab
      • In the Calculation section, click Manual
      • Click OK
      • On the File menu, click Open and try to open the file
      Use external references to link to the corrupted file
      • This method retrieves only data and not formulas or values from the workbook
        • On the File menu click Open
        • Browse from the current folder to the folder that contains the damaged file
        • Click Cancel
        • Click New on the File menu
        • Click Workbook
        • Click OK
        • Type =File Name!A1 in cell A1 of the new workbook, where File Name is the name of the damaged workbook
        • If the Select Sheet dialog box appears, select the appropriate sheet
        • Click OK
        • Select cell A1
        • On the Edit menu, click Copy
        • Select an area that is approximately the same size as the range of cells that contain data in the damaged file
        • Click Paste on the Edit menu
        • With the range of cells still selected, right click anywhere in the selected area and click copy
        • On the Edit menu, click Paste Special
        • Select Values
        • Click OK
    If a chart is linked to the corrupted file, use a macro to extract the data
    • This step removes the links to the damaged file and leaves only the data.
      • Enter the following macro code in a module sheet:
        
        1. Sub GetChartValues97()
        2. Dim NumberOfRows As Integer
        3. Dim X As Object
        4. Counter = 2
        5.
        6. ' Calculate the number of rows of data.
        7. NumberOfRows = UBound(ActiveChart.SeriesCollection(1).Values)
        8.
        9. Worksheets("ChartData").Cells(1, 1) ="X Values"
        10.
        11. ' Write x-axis values to worksheet.
        12. With Worksheets("ChartData")
        13. .Range(.Cells(2, 1), _
        14. .Cells(NumberOfRows + 1, 1)) = _
        15. Application.Transpose(ActiveChart.SeriesCollection(1).XValues)
        16. End With
        17.
        18. ' Loop through all series in the chart and write their values to
        19.
        20.
        21. ' the worksheet.
        22. For Each X In ActiveChart.SeriesCollection
        23. Worksheets("ChartData").Cells(1, Counter) = X.Name
        24.
        25. With Worksheets("ChartData")
        26. .Range(.Cells(2, Counter), _
        27. .Cells(NumberOfRows + 1, Counter)) = _
        28. Application.Transpose(X.Values)
        29. End With
        30.
        31. Counter = Counter + 1
        32. Next
        33.
        34. End Sub
      • Insert a new worksheet into your workbook and rename it ChartData
      • Select the chart from which you want to extract the underlying data values
      • Note: The chart can either be embedded on a worksheet or on a separate chart sheet
      • Run the GetChartValues97 macro.
      • The data from the chart will be placed in the ChartData worksheet

"Run-time Error 1004: Application or Object-Defined Error" Error Message When You Make Changes to the Excel Chart Legend
Error
• When you run a Microsoft Visual Basic for Applications (VBA) macro that uses the LegendEntries method to make changes to legend entries in a Microsoft Excel chart, you may receive the following error message:
  Run-time error '1004': Application or object-defined error
Cause
• This behavior occurs when the Excel chart contains more legend entries than there is space available to display the legend entries on the Excel chart
• When this behavior occurs, Microsoft Excel may truncate the legend entries
• Because the LegendEntries method in your VBA macro uses what appears for the legend (in this case, the truncated legend entries), the error message that is mentioned in the "Error" section of this article occurs when there are more entries than there is space available to display the legend entries on the Excel chart
Solution
• To work around this behavior, create a macro that reduces the font size of the Excel chart legend text before your VBA macro makes changes to the chart legend and then restore the font size of the chart legend so that it is similar to the following macro example
• Note: You must have an Excel chart on your worksheet for this macro to run correctly
  Sub ResizeLegendEntries()
  
  
  With Worksheets("Sheet1").ChartObjects(1).Activate
  ' Store the current font size
  fntSZ = ActiveChart.Legend.Font.Size
  
  'Temporarily change the font size.
  ActiveChart.Legend.Font.Size = 2
  
  'Place your LegendEntries macro code here to make
  'the changes that you want to the chart legend.
  
  ' Restore the font size.
  ActiveChart.Legend.Font.Size = fntSZ
  End With
  
  End Sub

Fields Are Not Mapped Correctly When You Use The Import Text Wizard To Import A Comma-Delimited Text File
Error
When you import a comma delimited text file by using the Import Text Wizard, the following behaviors occur:
• When you import a text file by using the Import Text Wizard, a field that contains data that exceeds the range of Long Integer is still mapped to the Long Integer.
• When you import the same file by using the TransferText method, the field is now correctly mapped to the Double data type. However, another field that contains alphanumeric characters is incorrectly mapped to the Double data type.
Solution
• Start Access
• Create a new database
• On the File menu, point to Get External Data
• Click Import
• In the Import dialog box, click Text Files in the Files of type section
• Locate the Source.txt file
• Click the text file
• Click Import
• In the Import Text Wizard, click Advanced
• In the Import Specification dialog box, in the Field Information section, click the row selector for the Field5 field
• Click the Data Type column
• In the list box, click Double
• Click OK to close the Import Specification dialog box
• Click Next in the Import Text Wizard
• Click Finish to close the Import Text Wizard
• Click OK in the message box
• In the Database window, click Tables
• Double-click the Source table to open it
• Note: that the ESN field is correctly mapped to the Double data type, and the data is imported.
Steps to Reproduce the Problem
• Create the comma delimited text file
  • Start Notepad
  • Paste the following text in Notepad
    MasterPack,QCSN,FNCI,MyHex,ESN.P1005C4J5,N108B08V4,FN
    CI21000000037,7402051F,11600132383P1005C4J5,N108B08T5,FNC
    I21000000069,74020522,11600132386
  • Save the file as source.txt
• Import the Text File into the Access Database
  • Start Access
  • Create a new database
  • On the File menu, point to Get External Data
  • Click Import
  • In the Import dialog box, click Text Files in the Files of type section
  • Locate the Source.txt text file
  • Click the text file
  • Click Import
  • In the Import Text Wizard dialog box, click Next
  • Click Next in the other Import Text Wizard dialog boxes
  • Click Finish to exit the Import Text Wizard
  • Click OK in the message box
  • In the Database window, click Tables
  • Right-click the source table
  • Click Design View to open the table in Design view
  • Click the row selector for the Field5 field
  • Verify the Field Size value in the Field Properties pane
    You may see that the Field Size is populated with the Long Integer value
  • Close the Design view window, and then double-click the source table to open the table in Datasheet view
    The data that corresponds to the Field5 column is not imported
  • Close the table
• Use the TransferText Method
  • In the Database window, click Modules in the Objects section
  • Click New
  • On the View menu, click Immediate Window
  • Type the following information, and then press Enter:
    DoCmd.TransferText acImportDelim,
    "Source_DataViaCode", "C:\Source.txt", True
  • Close the Visual Basic Editor
  • In the Database window, click Tables
  • Right-click the Source_DataViaCode table
  • Click Design View to open the table in Design view
  • Click the row selector for the ESN field
  • Verify the Field Size value in the Field Properties pane
  • Click the row selector for the MyHex field
  • Verify the Field Size entry in the Field Properties pane
  • Note that the ESN field is correctly mapped to the Double data type, but the MyHex field is also incorrectly mapped to the Double data type

You Receive An Error Message When Importing, Exporting Or Linking Text Files
Error
• When you use the Export Text Wizard to import, export, or link a text file, you may receive the following error message:
  Invalid setting in Excel Key of the Engines section of the Windows Registry
Solution
• Use Registry Editor to modify a registry key.
  • Click Start
  • Click Run
  • In the Open box type
    regedit.exe
    (in Microsoft Windows 95, Microsoft Windows 98, or Microsoft Windows Millennium Edition)
    OR
    regedt32.exe
    (in Microsoft Windows NT or Microsoft Windows 2000)
  • Click OK
  • In Registry Editor, expand the following key:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4\Engines\Text
  • For the Format key, you see the following value:
    "DELIMITED()"
  • Change the value of the Format key to the following value:
    "CSVDelimited"
  • Quit Registry Editor

Skipped Fields Are Imported When You Import Data From A Comma-Delimited Text File To An Existing Table
Error
• When you import data from a comma-delimited text file to an existing table by using the Import Text Wizard, the data in the fields that you have selected to skip in the Import Specification dialog box are imported to the existing table.
Solution
• Save the Import Specification
  • Open the database that has the problem that is mentioned in the "Errors" section of this article.
  • On the File menu, point to Get External Data
  • Click Import
  • In the Import dialog box, click Text Files in the Files of type list
  • Locate and then select the text file that you have to import
  • Click Import
  • In the Import Text Wizard, click Next
  • Click to select First Row Contains Field Names
  • Click Advanced
  • In the Import Specification dialog box, in the Field Information pane, click to select the check boxes under the Skip column for the fields that you do not want to import
  • In the Import Specification dialog box, click Save As
  • In the Save Import/Export Specification dialog box, click OK
  • Click OK to exit the Import Specification dialog box
  • In the Import Text Wizard, click Next
  • Click to select the In an Existing Table check box
  • Then select the existing table where you want to import the data.
  • Click Next
  • Click Finish
  • Click OK when you receive the following message:
    Finished importing file CompletedPathOfTheTextFile to table TableName
• Import Data to a New Table
  • Open the database that has the problem that is mentioned in the "Errors" section of this article
  • On the File menu, point to Get External Data
  • Click Import
  • In the Import dialog box, click Text Files in the Files of type list
  • Locate and then select the text file that you have to import
  • Click Import
  • In the Import Text Wizard, click Next
  • Click to select the First Row Contains Field Names check box
  • Click Advanced
  • In the Import Specification dialog box, in the Field Information pane, click to select the check boxes under the Skip column for the fields that you do not want to import
  • Click OK to exit the Import Specification dialog box
  • In the Import Text Wizard, click Next
  • Click In a New Table
  • Click Next In the Import Text Wizard, click Next with the default Field Name and Data Type that are given
  • In the Import Text Wizard, click Let Access add primary key
  • Click Next
  • Click Finish to exit the Import Text Wizard
  • Click OK when you receive the following message:
    Finished importing file CompletedPathOfTheTextFile to table TableName
• Steps to Reproduce the Behavior
  • Start Microsoft Office Access, and then create a new database
  • In the new database, create a table that is named Employee, with the following columns:



Column Name

Data type--------------------EmplD

TextEmpnameTextEmpname

TextEmpnameText



• Define a primary key on the EmpID field.
• Create a sample comma-delimited text file. To do this, follow these steps:
  • Run Notepad
  • Paste the following text in Notepad:
    EmpID,EmpName111,John222,Jim
  • Save the file on drive C/ with the name Employee2.txt
• In the Access database window, point to Get External Data on the File menu
• Click Import
• In the Import dialog box, click Text Files in the Files of type list.
• Locate the text file Employee2.txt that you created in above, select the file
• Click Import
• In the Import Text Wizard, click Next
• Click to select the First Row Contains Field Names check box
• Click Advanced
• In the Import Specification dialog box, under Field Information, click to select the check box under the Skip column against all the required fields except for EmpID
• Click OK to exit the Import Specification dialog box.
• In the Import Text Wizard, click Next
• Click to select In an Existing Table Select table Employee2
• Click Next and then Finish
• Click OK when you receive the following message: Finished importing file C:\Employee2.txt to table Employee2.
• Open the Employee2 table
• Note: All the fields in the Employee2 table are populated, even when you have chosen to import only EmpID

Column Format On A Microsoft Excel Worksheet Is Lost Or Changed When You Import Or Link Data From Excel
Error
• The column format on a Microsoft Excel worksheet is lost or replaced with a different format after you import the data into Microsoft Access or create a link to the Excel worksheet.
Solution
• The settings are not lost when you import from or link to an HTML file
• You need to preserve the currency formats of an Excel worksheet
  • Open the Excel workbook.
  • On the File menu, click Save As
  • In the Save As dialog box, in the Save as type list, click Web Page
  • Click Selection: Sheet ClickSave
  • In Access, open the database into which you want to import the data.
  • On the File menu, point to Get External Data
  • Click Import
  • Select the HTML file that you created above
  • Note: that when the Import HTML wizard appears, the format of the sample data will not appear as expected.
  • Complete the steps of the Import HTML wizard.
  • Open the table in Datasheet view. Note that the currency symbol appears as it did in Excel
• Steps to Reproduce the Behavior
  • Open Control Panel
  • If you are running Microsoft Windows 2000:
    • Double-click Regional Options
    • Click the General tab Under Your locale (location), click English (United States)
    • Click the Currency tab
    • Set the Currency Symbol box to $
  • If you are running Microsoft Windows 98, Microsoft Windows Millennium Edition, or Microsoft Windows NT 4.0:
    • Double-click Regional Settings
    • Click the Regional Settings tab
    • Under Regional Settings
    • Click English (United States)
    • Click the Currency tab
    • Set the Currency Symbol box to $
  • Click OK
  • Close Control Panel
  • Start Microsoft Excel
  • Open a blank workbook
  • Type the following numbers in the first column:
    32
    12
    66
    41
    51
    
  • Select column A
  • On the Format menu, click Cells
  • In the Format Cells dialog box, click Currency under Category
  • Click English (United Kingdom) under Symbol
  • Click OK
  • Note the new formatting of the column
  • Save the workbook as Book1.xls
  • Quit Excel
  • Start Access
  • Create a new database
  • On the File menu, point to Get External Data
  • Click Import
  • Import the Book1.xls file that you created earlier
    When the Import Spreadsheet wizard appears, note the format of the sample data.
  • Click Finish to complete the import
  • Click OK on the informational message informing you that the table was created
  • Open Sheet1 in Datasheet view
  • Note: that the currency symbol appears as the United States dollar sign rather than as the United Kingdom pound symbol.

Unexpected Error From External Database Driver (8961)" Error Message When You Try To Import Dbase Files Into Access
Error
• When you try to import dBASE files into Access, you may receive the following error message:
  Unexpected error from external database driver (8961)
Solution
• Start Windows Explorer, and then browse to the Borland folder.
• If you cannot locate the folder, follow these steps.
• Note: Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.
  • Click Start
  • Click Search
  • Click All files and folders
  • In the All or part of the file name box, type Borland
  • In the Look in list, click My Computer
  • Click Search
• Rename the Borland folder as BorlandOld
  For example, rename C:\Borland as C:\BorlandOld
• Import the dBASE files again

Hyperlinks in Embedded Excel Workbook Do Not Work
Error
• When you click a hyperlink in an embedded Microsoft Excel workbook, Excel generates the following error and does not select the range indicated by the hyperlink
  An Unexpected Error Has Occurred
Cause
• This problem occurs when you embed either a new or existing Excel workbook
• The problem does not occur when you link to an existing workbook The error occurs with the following containers
  • Microsoft Visual C++ Application
  • Microsoft Visual Basic Application
  • Microsoft Access
  • Microsoft PowerPoint
  • Microsoft Outlook
  NOTE: The problem does not occur when you embed an Excel workbook in a Microsoft Word document
Solution
• To work around this problem, you can link to the Microsoft Excel workbook instead of embedding it
• Note: that a linked object cannot be edited in-place; the linked object will be opened in a new window for editing
Steps to Reproduce the Problem
• For illustration purposes, the following steps demonstrate the problem using Microsoft PowerPoint 2000 as the container
• Similar steps in the other containers listed in the "Cause" section of this article will generate the same error
  1. Start a new presentation in Microsoft PowerPoint 2000
  2. Click Object on the Insert menu
  3. When the Insert Object dialog box appears, select Microsoft Excel Worksheet in the Object Type list, and click OK
  4. The embedded workbook will be activated in-place
  5. With cell A1 selected, right-click and choose Hyperlink on the shortcut menu choose Place in this Document for Link to, type B5 for the cell reference, and then click OK
  6. Click the hyperlink in A1
  7. You receive the error
     An unexpected error has occurred
  8. To work around this problem, link to an existing Excel workbook
  9. To link to a workbook using the steps above, in step 3, when the Insert Object dialog box appears, select Create From File, click Browse to locate the workbook, check the Link checkbox, and then click OK

"No Preview Available" and "File Format Is Not Supported" Error Messages Occur When You Try to View Graphic Files
Error Messages
• You receive the following error message when you try to view the images by using Windows Picture and Fax Viewer:
  No preview available
• You receive error messages similar to the following when you try to view the images by using other graphics viewing or editing programs:
  File format is not supported
  OR
  File is corrupted
• Solution
  • Start AOL or CompuServe
  • On the Settings menu or the Access menu (as appropriate), click Preferences
  • Click Internet Properties (WWW) or WWW (as appropriate)
  • Click the Web Graphics tab
  • Click Never compress graphics
  • Click Apply
  • Click the General tab
  • Under Temporary Internet files, click Delete Files
  • Click OK if you are prompted to confirm the deletion
  • Click OK
• More Information
  • For more information about AOL, visit the following AOL Web site:
    http://www.aol.com
  • For more information about CompuServe, visit the following CompuServe Web site:
    http://www.compuserve.com

You Receive A "The Application Failed To Initialize Properly (0xc0150002)" Error Message When You Start An Office 2003 Program On A Windows XP Professional-Based Computer
Error
• When you start an Office 2003 program on a Microsoft Windows XP Professional-based computer, you may receive the following error message:
  • The application failed to initialize properly (0xc0150002). Click on OK to terminate the application.
Cause
• This behavior may occur if you install Office 2003 and Windows XP Service Pack 1a (SP1a) on your computer, and do any of the following:
  • You upgrade your Windows XP Home-based computer to Windows XP Professional
  • You reinstall Windows XP on your computer
  • You perform a repair of Windows XP on your computer
Solution
• After you do a windows repair you also have to reinstall the updates for windows
• Check the windows update page and install the updates again including SP 1
• After you reinstall the service pack, restart your computer

Office 2003 Cannot Run In "Windows 98/Windows Me" Compatibility Mode
Error
• Thank you for your help!
  
  Microsoft thanks you for taking the time to send us information about the program error that you just experienced. After investigating error reports provided by users like you, our engineers devised a work around for this problem. This article contains information that may help you avoid this problem in the future.
  
  Error signature
  
  This article describes a program error that can have the following error signatures:



Application Name	Application Version	Module Name	Module Version	Offset
------------------------	--------------------------	-----------------	--------------------	------------------
Winword.exe	11.0.5604.0	Mso.dll	11.0.5606.0	00059890
Outlook.exe	11.0.5510.0	Mso.dll	11.0.5606.0	00059890
Excel.exe	11.0.5612.0	Mso.dll	11.0.5606.0	00059890

• Note: The error signature may vary.
• When you work in one of the programs that are listed in the "Applies to" section, you may receive an error message that is similar to the following (where program name is one of the programs that is listed in the "Applies to" section of this article):
  Microsoft program name has encountered a problem and needs to close. We are sorry for the inconvenience. Please tell Microsoft about this problem. We have created an error report that you can send to help us improve program name. We will treat this report as confidential and anonymous. To see what data this error report contains, click here.
• Note: To view the details of the error signature, click the link in the following text:
  To see what data this error report contains, click here.
Solution
• Right-click Start
• Click Explore
• In Microsoft Windows File Explorer, click Search
• In the What do you want to search for area of Search Companion, click All files and folders
• In the Look in box, click Local Hard Drives
• In the All or part of the file name box, type the executable file name of the Office 2003 program that is causing the problem
• For example, type one of the following
  • If Microsoft Office Word 2003 is listed in the error message that is described in the "Error" section, type Winword.exe
  • If Microsoft Office Excel 2003 is listed in the error message that is described in the "Error" section, type Excel.exe
  • If Microsoft Office Outlook 2003 is listed in the error message that is described in the "Error" section, type Outlook.exe
• To start the search, click Search or click Search Now
• When the search is completed, there should be one or more items in the Search Results list
• If there is more than one item in the list, pick the item that has the correct program icon or that is in the correct folder
• For example, the default installation path for an Office 2003 program is C:\Program Files\Microsoft Office\Office11
• Right-click the item
• Click Properties
• On the Compatibility tab, click to clear the Run this program in compatibility mode for check box in the Compatibility area
• Click OK
• If you have to, repeat these steps for each item that you find in the Search Results window

Corrupt Normal.dot Causes Errors When Automating Word
Error
• One or more invalid Normal.dot template files may cause an out-of-process automation client to throw one of the following errors:
  HRESULT: 0x8001010A
  VB Error: -2147417846
  "The message filter indicated that the application is busy"
  
  HRESULT: 0x800A175D
  VB Error: 5981
  "Cannot open macro storage"
  
  HRESULT: 0x800A142D
  VB Error: 5165
  "Word cannot open the existing [square]"
Solution
• The Normal.dot template file used by Word might be corrupt
• If you are encountering one of the errors described in the Error section, you can temporarily rename the Normal.dot template to determine if it is the cause of the problem
• Certain installations of Word may yield more than one legitimate Normal.dot file
• These situations include multiple versions of Word running on the same computer or several user profiles on the same computer
  In these situations, pay special attention so that you rename the correct copy of Normal.dot
• Rename the Normal.dot file follow these steps
  • Quit all instances of Word, including WordMail
  • On the Windows taskbar, click Start, point to Find, and click Files or Folders
  • In the Named box, type Normal.dot
  • In the Look In box, select your local hard disk drive (or an alternate user template location if you are running Word from a network server).
  • Click Find Now to search for the file.
  • For each occurrence of Normal.dot that appears in the Find dialog box, right-click the file.
  • Click Rename on the shortcut menu.
  • Give the file a new name, such as OldNormal.dot or Normal-1.dot
  • Minimize the find dialog box
  • Restart your automation client to start Word
  • If Word starts correctly, you have resolved the problem.
  • In this case the problem is a damaged Normal.dot template.
  • You might need to change a few settings to restore your favorite options.
  • If the Normal.dot file you renamed contains customizations, such as styles, macros, or AutoText entries that cannot be easily recreated, you may be able to copy those customizations from the old Normal.dot file to the new Normal.dot file by using the organizer.
  • For more information about using the organizer do the following
    • Click Office Assistant
    • Type Using the Organizer
    • Click Search
    • Click Use Settings from Another Document or Template
  • If your toolbar customizations are stored in a custom toolbar, you should be able to copy them using the Organizer.
  • Unfortunately, if the customizations were made to one of Word's built-in toolbars you might need to recreate them after you rename your template because you cannot copy those changes with the Organizer

You Receive A "The Document Caused A Serious Error The Last Time It Was Opened" Error Message When You Open A Word 2003 Or Excel 2003 Document
Error
• When you try to open a file that Microsoft Excel 2003 or Microsoft Word 2003 could not open previously, you may receive the following error message:
  The document 'Filename' caused a serious error the last time it was opened. Would you like to continue opening it?
• You may receive this message every time you try to open the file
Cause
• This problem occurs because the file appears on the list of disabled files for the Microsoft Office program.
• The program adds a file to this list if the file causes a serious error, such as causing the program to quit unexpectedly (crash) during two or more tries to open it.
• This message allows you to avoid potential problems that may occur if you open the file
Solution
• To view the list of disabled files, on the Help menu, click About Microsoft Program
• Click Disabled Items
• To re-enable one of the listed items, click to select the item, and then click Enable
• Note: Although a file is enabled, the program may still not be able to open it. The file may still cause serious errors

Error Message: Microsoft Word Has Encountered a Problem and Needs to Close
Error
• When you start Microsoft Word or work with a document, you may receive the following error message:
  Microsoft Word has encountered a problem and needs to close. We are sorry for the inconvenience.
  
  If you were in the middle of something, the information you were working on might be lost.
  
  Restart Microsoft Word
  
  Please tell Microsoft about this problem.
  
  We have created an error report that you can send to help us improve Microsoft Word. We will treat this report as confidential and anonymous.
  
  To see what data this error report contains, click here.
• This article describes how you can determine the exact problem description and resolution when you receive this error message
Find the Solution
• Step 1: Search for the Specific Error Message
  • In the error message dialog box (as described in the "Error" section of this article), click "click here"
  • In the Error signature section, the error message appears similar to the following example



App Name	App Version	Module Name	Module Version	Offset
-----------------	-----------------	---------------------	-----------------------	------------------
winword.exe	10.0.2627.0	winword.exe	10.0.2627.0	0032a96d



• Note the specifics about the error signature. In particular, note the AppName, ModName, and Offset values.
• In the Address line of your Web browser, type http://support.microsoft.com/default.aspx, and then press Enter
• In the Search (KB) box, select All Microsoft Search Topics
• In the For solutions containing box, type the values that you noted for AppName, ModName, and Offset.
• Using the example error signature above, type
  winword.exe 0032a96d
• Note: If the AppName and ModName are the same, type just the values that you noted for ModName and Offset
• Click Search now
• If any search results are returned, click the link to view the article that is returned.
• If the problem that you are experiencing does not appear in the list, please continue to step 2
• Step 2: Troubleshoot Possible Causes of the Error
  Use a systematic approach to resolve various error messages and problems in Microsoft Word
  • For additional information about how to do this, check the article number below in the Microsoft Knowledge Base 322743 HOW TO: Troubleshoot Problems in Word 2002 If you still cannot resolve the problem, please follow step 3
• Step 3: Use an Automated Search for Other Possible Causes of the Error
  • Use the following Web address to see a list of articles about known problems that display this error message and the appropriate workaround or resolution for the problem.
  • If the problem that you are experiencing does not appear in the list or was not resolved by the earlier steps, contact $$$ Microsoft Support $$$and get your wallets out
    http://support.microsoft.com/common/canned.aspx?R=d&H=Microsoft Word has encountered a problem and needs to close&LL=&Sz=Microsoft Word has encountered a problem and needs

Errors Installing Office 2003
Symptoms
• When you try to start a Microsoft Office 2003 program such as Microsoft Office Word 2003, Microsoft Office Excel 2003, or Microsoft Office PowerPoint 2003 for the first time, you receive the following error message:
  • Installation Error: File not Found
    A required installation file file_name.CAB could not be found.
  • Original Installation Source Required:
  If you installed the program name from a CD, insert your CD. If you installed the program name over your computer network, locate the installation source on your network. Once you have located your installation source, click OK.
  • A required installation file SKU011.CAB could not be found
• Note: The file name generally is similar to SKUxxx.cab, where xxx corresponds to the second, third, and fourth characters of the product code
Cause
• This problem may occur if one of the following conditions is true:
  • You logged on by using a user account that has never run an Office 2003 program.
  • Source files in the <drive>:\MSOCache\All Users\90000409-6000-11D3-8CFE-0150048383C9 folder are missing
  • The <drive>:\MSOCache folder has been deleted.
• Note: <drive>> is the local drive where the MSOCache folder is located. The MSOCache folder is the folder where the Local Install Source (LIS) is copied when Office 2003 is installed. (By default, the folder is hidden.) To view the MSOCache folder, you must configure the operating system so that you can see the hidden files and folders. To do this, follow these steps:
  • Click Start, and then click My Computer
  • Click Folder Options on the Tools menu
  • Click the View tab
  • Click Show hidden files and folders under Hidden files and folders
  • Clear the Hide file extensions for known file types check box
Workaround
• To work around this problem, you have to provide the original installation source files location that you used to install the program. For example, use one of the following procedures when you receive the error message:
  • Insert the original Office 2003 program CD that you used to install Office 2003, and then click OK
  • Click Browse, locate the Office 2003 program installation folder on the network, and then click OK
• This error can also occur when you apply a patch to Office 2003. Additionally, the error occurs when a .cab file is missing from the Local Install Source.

Cannot Install the Necessary Files Due to Windows Installer Error 1605" Error Message When You Try to Start Word
Error
• When you try to start Microsoft Office Word 2003, you may receive the following error message:
  Microsoft Word cannot install the necessary files due to Windows Installer Error 1605
• Word does not start
Cause
• This issue may occur if there is a problem with a template in the Word Startup folder
Solution
• To resolve this issue, determine which template causes the issue, and then delete that template from the Word startup folder.
• To determine which template causes the issue, remove each template from the Word startup folder, and then test by trying to start Word
• Quit any running programs
  1. In Windows Explorer, click Folder Options on the Tools menu
  2. Click the View tab, click to select the Show hidden files and folders check box
  3. Click OK
  4. Locate the drive:\Documents and Settings\username\Application Data\Microsoft\Word\Startup folder, where drive refers to the drive that Windows is installed on and username refers to your user name
  5. On the File menu, point to New
  6. Click Folder
  7. Type Temp
  8. Press Enter
  9. Click the first template that is listed in the Startup folder
  10. Move it to the Temp folder
  11. Try to start Word
  12. If Word starts successfully, you have removed the conflicting template
  13. If you receive an error message, repeat steps 5 through 7 until Word starts successfully
  14. After you have determined which template causes the conflict, move all the non-conflicting templates from the Temp folder to the Startup folder
  15. Click the Temp folder
  16. Press Delete

Reference Source Not Found" Error Message When You Change Numbering Formats For A Caption In Word 2003
Error
• In Microsoft Office Word 2003, if you insert a caption in a document, insert a cross reference, and then insert another caption with a different numbering format, the cross reference displays the following error message
  Error! Reference Source not found
Cause
• This problem may occur if you click to select the Exclude label from caption check box in the initial caption

Document Actions Task Pane Disappears And You Receive An "Internal Error" Error Message When You Merge Two Office Solution Accelerator For Proposals Documents
Error
• When you click Save (or Save As) on the File menu when you edit your Microsoft Office Solution Accelerator for Proposals document in Microsoft Office Word 2003. You choose to save the file with the file name of an existing file, you will be prompted with the following message
  The file filename already exists.
  Do you want to:
  • Replace existing file.
  • Save changes with a different name.
  • Merge changes into existing file
• If you click Merge changes into existing file, the Document Actions task pane may disappear, and you may receive the following error message
  Internal error
  Solution
  • Reject the changes in your