The point shg was making is that changing a user's settings by rmoving menus, etc can potentially cause problems if the settings are not restored exactly.
The point shg was making is that changing a user's settings by rmoving menus, etc can potentially cause problems if the settings are not restored exactly.
Hope that helps.
RoyUK
--------
For Excel Tips & Solutions, free examples and tutorials why not check out my web site
Free DataBaseForm example
Sorry for the late reply, I've not had access to a machine for more than a few minutes at a time for the last couple of days.
Thanks to all for the replies. As I stated in my OP, I'm fairly new to this VB thing, and I wasn't aware that Excel was such an inherently non-secure environment.
I want to particularly thank shg for the multiple items of advice he offered -- I'm incorporating them all! The IgnoreRemoteRequests does indeed force another session to open if the user double-clicks on a workbook (is that what the other forum user meant by "instantiation"?).
The only remaining "chink in the armor" I can discern at this point is the user's ability to drag another workbook into the window. Shg's suggestion regarding the Workbook Deactivate event is useful, but unfortunately it only enables me to detect that another workbook has been opened AFTER that workbook's Workbook_Open or Auto_Open procedures have already executed, so a really malicious user could have concievably already caused some damage. What I'm working on now is a procedure that will automatically and privately notify me of such illicit activity, preferably by email. However, sending an email via a macro from the user's machine through Outlook will open a warning message on his screen, and I don't want that to occur, and it seems there's no way to prevent that. So maybe SMTP or MAPI is the way to go, but that doesn't appear to be too easy, either. We do have IM on all the machines at work, so perhaps that's an option, but I've never used it so I'm clueless about that, too.
Any suggestions, anyone?
Thanks again,
Mark
Re: email check out CDO: http://www.rondebruin.nl/cdo.htm
My Recommended Reading:
Volatility
Sumproduct & Arrays
Pivot Intro
Email from XL - VBA & Outlook VBA
Function Dictionary & Function Translations
Dynamic Named Ranges
Look at the AutomationSecurity property.... the Workbook Deactivate event is useful, but unfortunately it only enables me to detect that another workbook has been opened AFTER that workbook's Workbook_Open or Auto_Open procedures have already executed ...
I stand by my earlier comment on that.... so a really malicious user could have concievably already caused some damage.
Entia non sunt multiplicanda sine necessitate
DonkeyOte, thanks for that link. I'll try that stuff out as soon as I get back to the office, and see if it works there.
Thanks shg, but I've already tried that, and it's not effective against the Workbook_Open procedure in a workbook that's been dragged-and-dropped into the session.
There are currently 1 users browsing this thread. (0 members and 1 guests)
Bookmarks