MWE
05-31-2008, 05:38 PM
Assume two differnt MS applications, e.g., Word and Excel. I have a procedure that runs in Word that creates an Excel object, opens a target xls file, does things to that file, closes/saves it and then sets all objects to nothing. Simple enough.
Suppose I want the user to be able to "do things" with the open xls file? So now the Word proc creates an Excel object, opens a target xls file, transfers "control" to the user, the user fiddles with the xls file, control is passed back to the word proc, the word proc closes/saves the xls file, and then sets all objects to nothing. How might I do that?
One method that almost does everything is to hyperlink from word to the xls file. That nicely halts word, opens the xls file in a new window and allows the user to fiddle as much as he/she wants. The problem is that there is no guarantee that the user will properly close/save the xls file The other problem is that word and excel are examples of what I want to do. The more general case is any MS appl to any MS appl. Some appls do not support hyperlinking, e.g., Outlook (I think)
Suppose I want the user to be able to "do things" with the open xls file? So now the Word proc creates an Excel object, opens a target xls file, transfers "control" to the user, the user fiddles with the xls file, control is passed back to the word proc, the word proc closes/saves the xls file, and then sets all objects to nothing. How might I do that?
One method that almost does everything is to hyperlink from word to the xls file. That nicely halts word, opens the xls file in a new window and allows the user to fiddle as much as he/she wants. The problem is that there is no guarantee that the user will properly close/save the xls file The other problem is that word and excel are examples of what I want to do. The more general case is any MS appl to any MS appl. Some appls do not support hyperlinking, e.g., Outlook (I think)