G
GMGarrettson
Related to : Consequences of IE Browser click on html <a href> link to
open an EXCEL File with VBA Macros in an EXCEL Application Window or
an Internet Explorer Window.
During a recent user test, I encountered the following problem:
If the browser flag for SW Class excelsheet8 is set to open an excel
application window, everything works fine. If the browser flag is set
to open excel in an IE window, various commands from the VBA (such as
open workbook) cause the inevitable Runtime error 1004.
This is annoying, but not critical (solution is obvious: set the
flag!)
The problem is that when the Runtime Error Box is closed and then the
IE window with Excel is closed ("no" to question box about saving
changes) an excel process remains active in the task manager even
after all excel tasks disappear. Any second attempt to open the excel
file from the browser results in a "server not found" error in the
browser window. Attempts to open the excel file directly result in a
"file already open" error message.
So my question is:
1) what is the reason for the persistent excel process? Can error
trapping force a "clean" end to the associated process?
2) Can I get environment Info using VBA in the excel file to trap this
error-prone situation (excel with VBA in IE Window) and tell the user
to change the browser flag before proceeding? (possible combined with
the "clean" disengagement from point 1)
3) Can I provide a specific error.htm page to deal with this situation
an explain what needs to be done? (Does IE have an equivalent to error
numbers, so I can catch this type of "server not found" message?)
Anyone able to help?
Thanks in advance
G.M.Garrettson
open an EXCEL File with VBA Macros in an EXCEL Application Window or
an Internet Explorer Window.
During a recent user test, I encountered the following problem:
If the browser flag for SW Class excelsheet8 is set to open an excel
application window, everything works fine. If the browser flag is set
to open excel in an IE window, various commands from the VBA (such as
open workbook) cause the inevitable Runtime error 1004.
This is annoying, but not critical (solution is obvious: set the
flag!)
The problem is that when the Runtime Error Box is closed and then the
IE window with Excel is closed ("no" to question box about saving
changes) an excel process remains active in the task manager even
after all excel tasks disappear. Any second attempt to open the excel
file from the browser results in a "server not found" error in the
browser window. Attempts to open the excel file directly result in a
"file already open" error message.
So my question is:
1) what is the reason for the persistent excel process? Can error
trapping force a "clean" end to the associated process?
2) Can I get environment Info using VBA in the excel file to trap this
error-prone situation (excel with VBA in IE Window) and tell the user
to change the browser flag before proceeding? (possible combined with
the "clean" disengagement from point 1)
3) Can I provide a specific error.htm page to deal with this situation
an explain what needs to be done? (Does IE have an equivalent to error
numbers, so I can catch this type of "server not found" message?)
Anyone able to help?
Thanks in advance
G.M.Garrettson