Ошибка 1429 ole idispatch word

I have 2 separate applications that use ole automation to pass mail merge documents to MS word.

The relevent code is:

[==============================================]
*-* Setup and activate Word
oWord = CREATEOBJECT(«Word.Application»)

*-*  Document file location and file name
oDocument = oWord.Documents.ADD( gcTxtDocFile )

*-*  && .dat file location and file name
oWord.ActiveDocument.MailMerge.OpenDataSource( gcTxtDatFile )

oWord.ACTIVATE()
[=================================================]

The last line throws:
OLE IDispatch exception code 0 from Miocrosoft Word: Cannot activate application.

What I can’t figure out is that it only fails in one of the apps. the other one works fine. I copied the form and Word files  from 1 app to the other and made a few changes to filenamse and paths.

The files exist. I even tried the 2 files from the working app and still get the error.

I have run out of ideas of what to look for.

Any suggestions are appreciated.

Michael

No, we re not talking about a centuries-old battle here, we re talking about a series of error numbers. But we re certain you ll battle these four errors frequently while writing Automation code. These four errors are raised by the Automation server sending back an error code. Which one you get depends on how much information the server is willing to provide. This is the frustrating part: there isn t any categorical difference between these errors, and each error has a variety of meanings. These four errors return every possible problem from every Automation server; in contrast, FoxPro has hundreds of error messages!

Before you think that this is an awful design, remember that FoxPro is receiving the errors in a standard COM/Automation interface. There isn t any way to assign a unique error number to every possible error in every possible server even if we could ensure the errors are unique across servers, we d have error numbers larger than GUIDs, which would cause other problems.

So why is it so frustrating to work with these four errors? You can t tell the difference between a fatal error (the server has disconnected), a syntax error, and an error that can be fixed (like a divide by zero error) by the number. Yes, it is possible to keep a meticulous database of the text and number of each error for each server, but because of the volume of errors, it s very hard to track every error you come across and stay on-track with your development efforts.

As we said before, the difference between these errors is in the quantity of information the server is willing to provide. Error 1426, «OLE error code 0x,»is the most simplistic. It returns only a character string containing the hexadecimal number and a short message, for example: «OLE error code 0x800706ba: The RPC server is unavailable.» In your error handler, ERROR() returns 1426, and MESSAGE() returns «OLE error code 0x800706ba: The RPC server is unavailable.»

Errors 1427, 1428, and 1429 all appear to return similar information: an exception code followed by the message. While FoxPro sees them as different errors, their messages seem eerily similar. The differences may lie in what is returned in the AERROR() function.

Visual FoxPro s AERROR() function returns more information for an error. It builds an array with seven columns containing various information, depending on whether it is a FoxPro, OLE, or ODBC error. Help indicates that most FoxPro errors return nulls for most of the entries, with the exception of OLE errors 1427 and 1429, and ODBC error 1526. In fact, OLE errors 1426 and 1428 also make good use of AERROR().

Table 2 lists the contents of the resulting AERROR() array. Error 1426 sets only the first three values; the remaining four are set to null values. Errors 1427, 1428, and 1429 use up to seven columns of the array.

Error 1426 sets the first three columns. The first is the error number, which is the same as querying ERROR(). The second is the VFP error message the one that s displayed in the error dialog box, as in: «OLE error code 0x80020026: Unknown name.» This is the same string that is returned from the MESSAGE() function. The third column contains only a portion of the text string; it is the string returned from the OLE server. VFP adds some standard text to clarify the message; in the case of 1426, it s «OLE error code 0x.» While you can parse that out of the string, it s probably easier just to check the third column of the array, which contains the error code followed by the message: «80020026: Unknown name.» Actually, it s even easier to check SYS(2018), the most recent error message parameter function. The remaining AERROR() array columns are .Null., like any other VFP error.

Errors 1427 1429 fill all columns of the array (if the Help file and Help Context ID are available). As you can see from Table 1, the VFP message is a concatenation of a standard message («OLE IDispatch exception code «), the exception number (column 7), the application name (column 4), and finally the text of the OLE message (column 3). The text of the message (column 3) is also the value returned by SYS(2018), the most recent error message parameter, which is different from error 1426, which returns just the text (as in column 3). Actually, SYS(2018) returns only the first 255 characters of the message, which can be significant in longer messages, as we ll see later on.

To really see how frustrating handling these errors can be, a few examples are in order. The first example shows the range of how informative these errors can be. For example, imagine the following line of code (yes, it has a typo in it, to illustrate our point):

The resulting error message is shown in Figure 1.

Just a bit brief, no? Especially since our example has no fewer than five names in it: the references to oExcel, oChart, the ChartWizard method (which is the culprit here), the Sheets object, and the Range object. To be fair, VFP is reporting what it received from the server, so we can blame the server for its omission of one small, but very helpful, piece of information.

On the flip side, there s this error that comes from the following line of code. This line references a file that doesn t exist:

This error, number 1429, is shown in Figure 2.

This message is so unusually long and informative, the error message box actually has a scroll bar to allow you to read the full text of the message! The full text of the error message is as follows:

It was while testing this error that we found that SYS(2018) contains only the first 255 characters.

Another situation is that the same error number gives different kinds of errors that need to be handled differently. One kind of error is the syntax error, those pesky typos that the compiler usually catches, or the run-time notification that informs you that you ve reversed those two parameters. Another kind of error is when the user is notified that their system is improperly configured, or they ve made a mistake. Almost all FoxPro errors fall into one category or the other, so it s much easier to handle each individual error.

Errors 1426 1429 return errors in both of these categories (and any other category you can think of). To illustrate, let s pick on error 1426. We ve already talked about «OLE error code 0x80020026: Unknown name,» shown in Figure 1, which generally means there s a misspelled method or property in the code and the developer needs to fix the code. The error handler can gracefully skip this line, shut down the module, or whatever action is appropriate (ideally, the developer fixes this before it gets to the user!). In contrast to that situation, Figure 3 shows a different error: «OLE error code 0x800706ba: The RPC server is unavailable.» This error can show up on two occasions: when you re opening the server and it doesn t start up correctly (or doesn t start up all), or later, after your program opens the server, and the user closes it before your program is finished with it. Another 1426 classic is «OLE error code 0x80080005: Server execution failed.» This means that the server is registered, but the actual EXE file isn t found (usually due to the user uninstalling by deleting the folder instead of using the Uninstall routine). These last two errors are handled a bit differently than a syntax error! Who knows how many other errors are returned as 1426.

Copyright 2000 by Tamar E. Granor and Della Martin All Rights Reserved

Click here follow the steps to fix Microsoft Visual Foxpro Error 1429 and related errors.

Instructions

Note:
This article was updated on 2023-04-04 and previously published under WIKI_Q210794

What is Microsoft Visual Foxpro Error 1429 error?

The Microsoft Visual Foxpro Error 1429 error is the Hexadecimal format of the error caused. This is common error code format used by windows and other windows compatible software and driver vendors.

This code is used by the vendor to identify the error caused. This Microsoft Visual Foxpro Error 1429 error code has a numeric error number and a technical description. In some cases the error may have more parameters in Microsoft Visual Foxpro Error 1429 format .This additional hexadecimal code are the address of the memory locations where the instruction(s) was loaded at the time of the error.

What causes Microsoft Visual Foxpro Error 1429 error?

The Microsoft Visual Foxpro Error 1429 error may be caused by windows system files damage. The corrupted system files entries can be a real threat to the well being of your computer.

There can be many events which may have resulted in the system files errors. An incomplete installation, an incomplete uninstall, improper deletion of applications or hardware. It can also be caused if your computer is recovered from a virus or adware/spyware
attack or by an improper shutdown of the computer. All the above actives
may result in the deletion or corruption of the entries in the windows
system files. This corrupted system file will lead to the missing and wrongly
linked information and files needed for the proper working of the
application.

How to easily fix Microsoft Visual Foxpro Error 1429 error?

There are two (2) ways to fix Microsoft Visual Foxpro Error 1429 Error:

Advanced Computer User Solution (manual update):

1) Start your computer and log on as an administrator.

2) Click the Start button then select All Programs, Accessories, System Tools, and then click System Restore.

3) In the new window, select «Restore my computer to an earlier time» option and then click Next.

4) Select the most recent system restore point from the «On this list, click a restore point» list, and then click Next.

5) Click Next on the confirmation window.

6) Restarts the computer when the restoration is finished.

Novice Computer User Solution (completely automated):

1) Download (Microsoft Visual Foxpro Error 1429) repair utility.

2) Install program and click Scan button.

3) Click the Fix Errors button when scan is completed.

4) Restart your computer.

How does it work?

This tool will scan and diagnose, then repairs, your PC with patent
pending technology that fix your windows operating system registry
structure.
basic features: (repairs system freezing and rebooting issues , start-up customization , browser helper object management , program removal management , live updates , windows structure repair.)