Word Object Library Serious compatability problem with VB -Useful Info
Micorsoft knows this problem exists but has done nothing to fix the Word library itself. It took a week to find the answer to this problem....
The VB interface crashes when a reference is set to the word object library as soon as you DIM something...
here is the Answer.................
Fix the Word Object library
BUG: Automation Client Receives Error or Crashes Calling Word's Find Object
This article applies to…
This article was previously published under Q292744
SYMPTOMS
When you use an out-of-process client application that uses early binding to Automate Word 97 or later, the application may crash with an access violation or you may receive one of the following error messages:
From Microsoft Visual Basic:
The Interface will simply carash as soon as you insert a space after the Variable Name.. (The article at the link doesn't mention this this is why i had so much trouble finding the solution.
Run-time error '-2147023113 (800706f7)':
The method '~' of object '~' failed
Run-time error '-2147023113 (800706f7)':
Method 'Execute' of object 'Find' failed
Run-time error 430:
Class does not support automation or does not support expected interface.
From Microsoft Visual C++:
HRESULT = 0x800706F7
RPC_X_BAD_STUB_DATA - The stub received bad data.
NOTE: In debug builds you receive a corrupt stack warning from an Assert dialog box, and the value of EAX is that listed above. In release builds, the stack corruption will likely crash the application soon after this point, but the HRESULT value is likely to be similar to the above.
The problem occurs consistently on some computers, but may never occur on others. Installing a new application or a Microsoft Excel service pack can cause a computer that was working previously to experience the problem.
The information in this article applies to:
Microsoft Office Word 2003
Microsoft Word 2002
Microsoft Word 2000
Microsoft Word 97 for Windows
Microsoft Visual Basic Professional Edition for Windows 6.0
Microsoft Visual Basic Enterprise Edition for Windows 6.0
Microsoft Visual C++, 32-bit Professional Edition 6.0
Etc....
Regarding the error numbers..... I am simply quoting microsoft
If you went to the link provided you would see it is a microsoft document and nothing to do with me..
I had the porblem and could not reolve it for a week, which as you might guess could be very bad for progress...
Thus if you had the problem this info would be very important to you..
with respect
Steve