You're right. I misread the question.

Could the code simply be waiting for the worksheet cell selection to change?
If you don't go to another cell, the code doesn't fire.

--
HTH,
Gary Brown

If this post was helpful to you, please select ''YES'' at the bottom of the
post.



"Jack" wrote:

Which code?
I think you do not understand my post.
That routine is fired EACH time you click on the sheet!!!!
Jack

"Gary Brown" wrote in
message ...
Could the code simply be waiting for the worksheet selection to change?
If you don't go to another worksheet, the code doesn't fire.

--
HTH,
Gary Brown

If this post was helpful to you, please select ''YES'' at the bottom of
the
post.



"Jack" wrote:

<I had posted that in vbasic newsgroup 3 days ago but I had no response

==========
Talking about:

Private Sub moExcelApp_SheetSelectionChange(ByVal Sh As Object, ByVal
Target
As Excel.Range)
<my code
End Sub

Can I place my code safely inside that subroutine or are there some
timing
restrictions?

There must be some timing limitations, because when I step through the
code
in that routine (place a breakpoint), MsExcel starts flashing and
displays
message that it waits for OLE operation to be completed or something like
that.
Where I can read about it more?
Jack


Your comments appreciated,
Jack