Home |
Search |
Today's Posts |
#1
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
I'm having some trouble with consistently getting Excel to fire the
newWorkbook event when I open Excel. It seems that on some computers, opening excel (which opens book1.xls by default) invokes the newWorkbook event while on others, it does not. This doesn't appear to be an issue of version as I have two workstations with the same version of excel (11.6560.6568) sp2 with one firing the newWorkbook event when I open Excel and one not. |
#2
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
Hi Jeff,
If you haven't already looked, the first thing that comes to mind is the Excel macro security setting. Go to Tools Macro Security... and make sure that security is not set to "High." -- Ken Hudson "Jeff" wrote: I'm having some trouble with consistently getting Excel to fire the newWorkbook event when I open Excel. It seems that on some computers, opening excel (which opens book1.xls by default) invokes the newWorkbook event while on others, it does not. This doesn't appear to be an issue of version as I have two workstations with the same version of excel (11.6560.6568) sp2 with one firing the newWorkbook event when I open Excel and one not. |
#3
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
No, unfortunately it's not that simple. I've set macro security to low and
it still doesn't fire off. To make sure I'm very specific, this isn't a problem if I click CTRL-N for a new workbook once I'm inside of Excel. Creating a new workbook this way is just fine & dandy. The newWorkbook event is fired every time. However, the workbook shell that is opened by default by Excel when the excel.exe application is launched does not appear to invoke the normal events on a client-by-client basis.... A workaround is to open Excel with the /e switch but I don't want all my customers to do this. Per Microsoft, the /e switch "forces Excel to start without creating a new workbook(Book1.xls)." So, it's something about that new workbook that excel creates automatically that is different. I just need a bit of help figuring out why that workbook invokes the newWorkbook methods on some machines and not others. "Ken Hudson" wrote: Hi Jeff, If you haven't already looked, the first thing that comes to mind is the Excel macro security setting. Go to Tools Macro Security... and make sure that security is not set to "High." -- Ken Hudson "Jeff" wrote: I'm having some trouble with consistently getting Excel to fire the newWorkbook event when I open Excel. It seems that on some computers, opening excel (which opens book1.xls by default) invokes the newWorkbook event while on others, it does not. This doesn't appear to be an issue of version as I have two workstations with the same version of excel (11.6560.6568) sp2 with one firing the newWorkbook event when I open Excel and one not. |
Reply |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Forum | |||
New instance of excel.exe not firing newWorkbook event | Excel Programming | |||
New instance of excel.exe not firing newWorkbook event | Excel Programming | |||
OnTime event not firing in Workbook_Open event procedure | Excel Programming | |||
Excel NewWorkbook event | Excel Programming | |||
C# newWorkbook event | Excel Programming |