Access 2003 Solution Center | Troubleshooting - Access 2003- In Office programs, you receive a "Specified COMMAND search directory had too many parameters" error message when you try to use an MS-DOS core command from the Shell function
This article describes an issue when you attempt to use DOS core commands from the Shell function in a Visual Basic for Applications macro. - "Error 1919. Error configuring ODBC data source" error messages when you run the Setup program for Office
Describes an error message that you receive when you install an Office program. - You may receive the "Word was unable to open the data source" error message when you try to mail merge to Word by using an Access parameter query in Microsoft Access
Describes the "Word was unable to open the data source" error message. You may receive this error message when you mail merge to Word by using an Access parameter query. - Word 2003 Mail Merge stops responding with "Word was unable to open the data source" error message when you use an Access parameter query in Access 2003
Describes the problem that occurs when you use the Mail Merge Wizard to merge the data from an Access 2003 parameter query into a Word 2003 Mail Merge document. You receive an error message. Includes 2 resolutions methods and the steps to reproduce. - List of error codes and error messages for Windows Installer processes in Office 2003 products and Office XP products
Lists the error codes and error messages that may appear may appear in the Windows Installer log file. The error code values and descriptions can help you diagnose installation problems. - GetObject or GetActiveObject cannot find a running Office application
When you try to use GetObject (Microsoft Visual Basic) or GetActiveObject (Microsoft Visual C++) to automate a Microsoft Office application, you get one of the following error messages, even though the Office application is running: Error message 1... - PRB: Office 97 Automation Client Fails After Re-compilation with Office 2000 or Later Type Library
An Automation client that successfully automated an Office 97 application crashes with the same Office 97 application after the program is recompiled using an Office 2000 or later type library. You might receive an error similar to one of the... - BUG: Office repaint problem if modal form is shown from ActiveX EXE
When a modal form is displayed from an ActiveX EXE component called from VBA, the Microsoft Office application that made the call does not repaint correctly while the dialog is displayed. - BUG: Hyperlinks in Embedded Excel Workbook Do Not Work
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: - The "Import/Link Data on an FTP or HTTP Server" Help topic is not correct in Access 2000, Access 2002, Access 2003 and Access 2007
In Microsoft Access 2000, Microsoft Access 2002, Microsoft Office Access 2003, and Microsoft Office Access 2007, the Help topic "Import or link (read-only) data on an FTP or HTTP Internet Server" incorrectly states that you can import or link data from... - An Access Snapshots (*.snp) object looks distorted when you insert the object in PowerPoint
If you insert an Microsoft Office Access Snapshot file in Microsoft Office PowerPoint, a border appears around the snapshot object. Additionally, the object may be too large for its border (zoomed). Alternatively, the object may be cut off on one or... - You receive incorrect results from an Outer Join query
Describes a problem that occurs when you run a Left Outer Join or a Right Outer Join query. Access may return incorrect data. Corrected in Jet 4.0 Service Pack 4 (SP4) and later versions. Includes steps to reproduce the problem.
- How to work with the Outlook E-mail Security Update in an Access database
Describes that you may receive "A program is trying to automatically send e-mail on your behalf" message when you run the SendObject macro action. Or, you may receive a "run-time error '2293'" when calling the SendObject VBA method in Access. - BUG: Access object model breaks binary compatibility
Automation clients written for Microsoft Access 97 that use either early binding (VB, ATL with #import) or dispid binding (MFC) might unexpectedly fail when trying to automate Microsoft Access 2000, Microsoft Access 2002, Microsoft Office Access 2003,... - Microsoft Jet database engine 4.0 enforces the syntax "Is Null"
Describes the symptons that you experience if you use "= Null" instead of "Is Null". You will not get the expected results. This behavior is by design before version 4.0 of the Microsoft Jet database engine. - ACC2000: Changes That You Make to Referenced Projects Are Not Saved in Visual Basic Editor
In Microsoft Visual Basic for Applications, you can reference another VBA project (MDB, MDA, or ADP) in the References dialog box. By using the Project Explorer in the Visual Basic Editor, you can also see the code in referenced projects, or you can... - You cannot use a pound character in a file name for a hyperlink in an Office program
When you create a hyperlink to another file, the file name that appears in the hyperlink text may appear to be different than the actual file name. For example, a hyperlink to a file with the following file name: C:\My Documents\Book#One.xls may appear... - Reset method of CommandBars rebuilds menu bar only
When you reset a menu on a built-in menu bar using Microsoft Visual Basic for Applications code, none of the menu items are available. - WD: Inserting Database in Word Document Does Not Retain Pictures
When you use a Microsoft Access or Microsoft FoxPro database in a Word document (for example, a Word mail merge), pictures in the database do not appear. When you use DDE (dynamic data exchange) to insert the database, you receive the following error... - Error message when you try to add tables to the Relationships window in Access: "There is not enough memory to perform this operation. Close unneeded applications and then try the operation again"
Discusses behavior that occurs if the tables contain more than approximately 1,200 columns. Describes a workaround for this behavior. - How to use dBASE data with Access and Jet
Describes an issue about updating data to a linked dBASE file from within Access 2000 or from within a Jet 4.0 application. Requires that you install the latest Jet 4.0 service pack or BDE to resolve the issue. - Name AutoCorrect Does Not Repair Query Field/Table Names
When you have the Name AutoCorrect feature enabled, and you make changes to a query's record source, such as changing a table name, a query name, or a field name, and you then run the query, the query may: Prompt for the old field name value. Return... - ACC2000: Using File DSN to Import or Link a FoxPro ODBC Data Source Causes Reserved Error -7778
When you use a File DSN to import or link a FoxPro ODBC data source, you may receive the following error: - Error message when you try to update a record on a form in an Access database: "This Recordset is not."
Discusses a problem in which you may receive an error message when you try to update a record on a form in an Access database. - Function called from command bar control runs three times in Access
Explains why a function that is called from the command bar control runs three times in Access 2000 and in Access 2003. To work around this problem, you can store the procedure in the standard module instead of in the class module.
|
| |