Home |
Search |
Today's Posts |
#1
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
hello,
When debugging my "Worksheet_Cahnage" code I cannot get my breakpoint to work when I have run one worksheet change and the started to debug. When I Reset the debug session and starts with a new WS Change, my program does not stop on my breakpoint in the Worksheet_change procedure... Why? It seems like the VB-code does not detect the a WS Change if I have broken (reset) my execution when debugging... Please help someone. I have to bring Excel down and startup again to be able to continue debugging... /kopego |
#2
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
Hi
have you disabled application.enableevents at he beginning of your event proecedure and not enabled it back again after stopping the execution of the first call to this event procedure? "konpego" wrote: hello, When debugging my "Worksheet_Cahnage" code I cannot get my breakpoint to work when I have run one worksheet change and the started to debug. When I Reset the debug session and starts with a new WS Change, my program does not stop on my breakpoint in the Worksheet_change procedure... Why? It seems like the VB-code does not detect the a WS Change if I have broken (reset) my execution when debugging... Please help someone. I have to bring Excel down and startup again to be able to continue debugging... /kopego |
#3
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
If so, you can type
Application.EnableEvents = True in the immediate window. If it works then, this will prove Frank's point. -- HTH RP (remove nothere from the email address if mailing direct) "Frank Kabel" wrote in message ... Hi have you disabled application.enableevents at he beginning of your event proecedure and not enabled it back again after stopping the execution of the first call to this event procedure? "konpego" wrote: hello, When debugging my "Worksheet_Cahnage" code I cannot get my breakpoint to work when I have run one worksheet change and the started to debug. When I Reset the debug session and starts with a new WS Change, my program does not stop on my breakpoint in the Worksheet_change procedure... Why? It seems like the VB-code does not detect the a WS Change if I have broken (reset) my execution when debugging... Please help someone. I have to bring Excel down and startup again to be able to continue debugging... /kopego |
Reply |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Forum | |||
breakpoint calculation | Excel Worksheet Functions | |||
breakpoint calculation | Excel Worksheet Functions | |||
SQL fails without breakpoint | Excel Programming | |||
worksheet_change vs. calculate, and worksheet_change not running | Excel Programming | |||
worksheet_change vs. calculate, and worksheet_change not running | Excel Programming |