CLIENT_OLE2 just not working for me

Question

The following code is working for me.
My form displays message "1", but not message "2". MS Word is opened, but a new document is NOT created.
Any suggestions?
Thanks,
-Ken
PROCEDURE new_doc IS
  MyApplication client_ole2.OBJ_TYPE;
  MyDocuments client_ole2.OBJ_TYPE;
  MyDocument client_ole2.OBJ_TYPE;
  MySelection client_ole2.OBJ_TYPE;
Begin
  MyApplication := client_ole2.CREATE_OBJ('Word.Application');
  client_ole2.SET_PROPERTY(MyApplication, 'Visible', true);
  MyDocuments := client_ole2.GET_OBJ_PROPERTY(MyApplication, 'Documents');
message('1');
  MyDocument := CLIENT_OLE2.INVOKE_OBJ(MyDocuments,'add');
message('2');
  Myselection := CLIENT_OLE2.GET_OBJ_PROPERTY(Myapplication,'Selection');
message('3');
  client_ole2.SET_PROPERTY(Myselection,'Text', 'Hello World');
  client_ole2.RELEASE_OBJ(MySelection);
  client_ole2.RELEASE_OBJ(MyDocument);
  client_ole2.RELEASE_OBJ(MyDocuments);
  client_ole2.RELEASE_OBJ(MyApplication);
exception
  when others then message( error_text);
End;

Answer 1

Hi Ken,
Sorry to hear you're having such difficulties. CLIENT_OLE2 must be "working", since Word is being launched. Upon reviewing your code, I was shocked by its inconsistent use of lettercase, and thought that this almost certainly was causing your problem. For example, you declare objects MyApplication and MySelection, and later refer to them as Myapplication and Myselection.
My hunch was that this line:
  MyDocument := CLIENT_OLE2.INVOKE_OBJ(MyDocuments,'add');should have been
  MyDocument := CLIENT_OLE2.INVOKE_OBJ(MyDocuments,'Add');Surprisingly, I pasted your code into a test form, as-is, and it ran without a hitch. So I guess you're off the hook, here -- PL/SQL and OLE appear to be flexible with respect to lettercase. Many languages and environments are not so forgiving!
After giving it some more thought, I'm certain that the problem is not CLIENT_OLE2, but with your MESSAGE statements. Message 2 is causing Message 1 to "float" up as a modal dialog, which unfortunately is hidden behind Word. If you minimize Word, you will see this dialog. Once you dismiss it by clicking "OK", your code will proceed. Message 3 will cause Message 2 to "float" up in the same manner. If you comment out or remove all of your MESSAGE statements, everything should run as you are expecting.
Eric Adamson
Lansing, Michigan