J
JGeniti
Hopefully someone can shed some light on the problem I'm having.
I have a ton of Excel files that are shared on a network and that all
reference one shared add-in with all of the code. I was originally
having an issue when my users would have one of these files open and
try to open another excel file. To try to rectify that problem I added
Application.IgnoreRemoteRequests = True to a sub procedure in the
add-in that gets called by the WorkbookOpen event on the actual file.
When I had my first user test this it worked perfect. He could open all
different Excel files and they all opened as seperate instances of
Excel. The bad part was that every other network user that tried to
open any of the files linked to the add-in got a runtime error at
startup and couldn't access the code.
Even after I went back in and removed the code from the add-in it still
was causing problems for all of my users. I actually had to replace the
add-in with a previous version.
I'm not sure if my problem is due to the fact that I called the
IgnoreRemoteRequests method from the add-in as opposed to calling it
from within the actual workbook being opened or if there is just a
problem with Excel. I tried testing this by going to
Tools>Options>General and clicking the "Ignore other applications"
checkbox but I was unable to open any Excel Files after that. Once I
unchecked that option everything was good again.
Any help with this issue or even a better way to force Excel to open a
new instance whenever a file is opened would be greatly appreciated.
Thanks,
James
I have a ton of Excel files that are shared on a network and that all
reference one shared add-in with all of the code. I was originally
having an issue when my users would have one of these files open and
try to open another excel file. To try to rectify that problem I added
Application.IgnoreRemoteRequests = True to a sub procedure in the
add-in that gets called by the WorkbookOpen event on the actual file.
When I had my first user test this it worked perfect. He could open all
different Excel files and they all opened as seperate instances of
Excel. The bad part was that every other network user that tried to
open any of the files linked to the add-in got a runtime error at
startup and couldn't access the code.
Even after I went back in and removed the code from the add-in it still
was causing problems for all of my users. I actually had to replace the
add-in with a previous version.
I'm not sure if my problem is due to the fact that I called the
IgnoreRemoteRequests method from the add-in as opposed to calling it
from within the actual workbook being opened or if there is just a
problem with Excel. I tried testing this by going to
Tools>Options>General and clicking the "Ignore other applications"
checkbox but I was unable to open any Excel Files after that. Once I
unchecked that option everything was good again.
Any help with this issue or even a better way to force Excel to open a
new instance whenever a file is opened would be greatly appreciated.
Thanks,
James