View Single Post
  #2  
Old June 12th, 2004, 01:43 AM
Rob
external usenet poster
 
Posts: n/a
Default re; Worksheet_SelectionChange goes cold

Thanks for your advice, Mark. I think the whole procedure has become to
huge for me to understand enough to manipulate further. I posted the code
in response to Bob Phillip's reply which you may like to look at??

Rob

"Mark E. Philpot" wrote in message
...
If you are using 2 events for the same sheet, one of them
always goes first. You could "Call" the other event via
the first, whichever that is.

Mark
-----Original Message-----
Thanks for the suggestion Mark, but that is not the

problem. The event
occurs no matter how I enter the cell.....well 99.99% of

the time. It's the
0.01% times that's confusing as I don't do anything

different. What also
confuses the matter is, why should it begin to work again

after going into
the VBA and clicking reset??? AND why does the other

event still work in
the same cell?? It's just the userform that doesn't

appear.

Rob

"mark" wrote in

message
...
Gidday,

Maybe it only works when a set number of characters is
typed or does not change if text is pasted into cell or
only works when tab key or return key is pressed.

You may have to set the events to accept a key event or
lost focus event.

Mark


-----Original Message-----
Hi all,
I have a Worksheet_SelectionChange on a worksheet
together with a
Worksheet_Change event. The procedure generally works
great but every so
often, part of the Selection change does not perform as
it should. That is,
it is supposed to bring up a userform when a cell in a
certain column is
selected. As I said, this usually works, but now and
then, the user form
does not appear. The other strange thing is that that
same column/cell when
selected also brings up a message box should some
conditions not be met. If
the conditions are met, the userform appears. When the
procedure does not
work, the message box still appears if I un-meet a
condition but not the
userform.
The only way I can resolve this is to bring up the VBA
code and click the
reset button. Then all's well again. It does not say

it's
in break mode when
it isn't working as that would mean all the change

events
would be disabled,
but they're not!
I cannot see any change or action happening when I

click
the reset button.
All I know is that when doing that, the procedure and
userform will work
faultlessly again as it should.

Has anybody got any clues? It's very annoying as it

only
occurs
infrequently and although I can resolve the problem,

the
program is intended
to be used by another user.

Rob


.



.