Home |
Search |
Today's Posts |
|
#1
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
Although CreateEventProc ensures the event is correctly written, providing
the control already exists, it has the possible disadvantage of opening the VBE to display the new event. Also I very much doubt it would prevent the crash problem, which I'd bet is related to an untimely recompile of the project while the code is running. That depends of course on what you are doing overall as I mentioned previously. In the AddLabel routine I posted, forgot to remove a couple of lines accidentally left in for my own testing. Set ole = ws.OLEObjects(2) and a bit further down - Set ole = ws.OLEObjects(1). Regards, Peter T "Amit Kumar" wrote in message ... I already tried using CreateEventProc... But getting same error. "Robert Bruce" wrote: Yn newyddion: , Roedd Peter T <peter_t@discussions wedi ysgrifennu: I've amended your routine slightly and with the test all seems to work OK. Having said that, there are scenarios where adding event code to class modules can cause the project to recompile and crash Excel (eg under certain circumstances when adding new code to the project that's running the insert new code). If the following doesn't work it's probably related to what you are doing overall. See also the CreateEventProc method. Rb |
Reply |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Forum | |||
adding code lines with vba code | Excel Programming | |||
Application makes VBE crash. How do I troubleshoot? | Excel Programming | |||
Adding code to control on form causes Excel to crash | Excel Programming | |||
Adding code to a control on a form causes excel to crash | Excel Programming | |||
Application.Quit en Excel crash | Excel Programming |