![]() |
Capturing Excel Opening
I'm planning to put Excel on a few users' machines, but I want to set it up
in such a way that Excel won't open if they haven't met some external conditions. So they do the usual choice of things to fire up Excel.exe, but if the conditions aren't met, eg. outside office hours, then they get a message saying "XYZ Condition not met, etc. Try again later". I can see how to do this simply using a workbook containing VBa in XLStart, or perhaps using startup switch on Excel to open such workbook, but my wiley users would soon find this and delete it. Is there any way of doing something more robust, such as modifying a dll that would trigger my test (eg. a little exe file "conditionsmet.exe"), that if the condition wasn't met Excel would not open? Any ideas greatly appreciated, TIA, Dranz |
Capturing Excel Opening
perhaps rename excel.exe to something else,
then set up a BAT file or other executable named excel.exe that would do what you want (including start excel if appropriate). -- Regards, Tom Ogilvy "Dransfield" wrote in message ... I'm planning to put Excel on a few users' machines, but I want to set it up in such a way that Excel won't open if they haven't met some external conditions. So they do the usual choice of things to fire up Excel.exe, but if the conditions aren't met, eg. outside office hours, then they get a message saying "XYZ Condition not met, etc. Try again later". I can see how to do this simply using a workbook containing VBa in XLStart, or perhaps using startup switch on Excel to open such workbook, but my wiley users would soon find this and delete it. Is there any way of doing something more robust, such as modifying a dll that would trigger my test (eg. a little exe file "conditionsmet.exe"), that if the condition wasn't met Excel would not open? Any ideas greatly appreciated, TIA, Dranz |
Capturing Excel Opening
That's a good idea - do you know how I can stop the renamed Excel.exe having
the Excel icon, and make the new BAT file have the Excel icon? "Tom Ogilvy" wrote in message ... perhaps rename excel.exe to something else, then set up a BAT file or other executable named excel.exe that would do what you want (including start excel if appropriate). -- Regards, Tom Ogilvy "Dransfield" wrote in message ... I'm planning to put Excel on a few users' machines, but I want to set it up in such a way that Excel won't open if they haven't met some external conditions. So they do the usual choice of things to fire up Excel.exe, but if the conditions aren't met, eg. outside office hours, then they get a message saying "XYZ Condition not met, etc. Try again later". I can see how to do this simply using a workbook containing VBa in XLStart, or perhaps using startup switch on Excel to open such workbook, but my wiley users would soon find this and delete it. Is there any way of doing something more robust, such as modifying a dll that would trigger my test (eg. a little exe file "conditionsmet.exe"), that if the condition wasn't met Excel would not open? Any ideas greatly appreciated, TIA, Dranz |
Capturing Excel Opening
I don't. Maybe someone else does.
-- Regards, Tom Ogilvy "Dransfield" wrote in message ... That's a good idea - do you know how I can stop the renamed Excel.exe having the Excel icon, and make the new BAT file have the Excel icon? "Tom Ogilvy" wrote in message ... perhaps rename excel.exe to something else, then set up a BAT file or other executable named excel.exe that would do what you want (including start excel if appropriate). -- Regards, Tom Ogilvy "Dransfield" wrote in message ... I'm planning to put Excel on a few users' machines, but I want to set it up in such a way that Excel won't open if they haven't met some external conditions. So they do the usual choice of things to fire up Excel.exe, but if the conditions aren't met, eg. outside office hours, then they get a message saying "XYZ Condition not met, etc. Try again later". I can see how to do this simply using a workbook containing VBa in XLStart, or perhaps using startup switch on Excel to open such workbook, but my wiley users would soon find this and delete it. Is there any way of doing something more robust, such as modifying a dll that would trigger my test (eg. a little exe file "conditionsmet.exe"), that if the condition wasn't met Excel would not open? Any ideas greatly appreciated, TIA, Dranz |
All times are GMT +1. The time now is 02:07 AM. |
Powered by vBulletin® Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
ExcelBanter.com