View Single Post
  #6   Report Post  
Posted to microsoft.public.excel.programming
[email protected] TheObstacleIsThePath@gmail.com is offline
external usenet poster
 
Posts: 17
Default simple vb question

On Sep 15, 11:25*am, Gary''s Student
wrote:
The problem can be avoided by using the Deactivate Event rather than the
Activate Event.

Let's say that for each worksheet we have a Deactivate macro that just
records the address of the activecell in a public, static, string variable.

That way, any time a worksheet and been activated and then deactivated, any
other sheet will have direct access to the other sheet's most recent active
cell.

Thus you can avoid the "bouncing" behavior in my previous post.
--
Gary''s Student - gsnu2007k


This is what I had before coming to the Newsgroup. The problem was
that the subroutine that kept track of the row was triggered every
time I moved to a new cell -- it made it cumbersome to navigate
because of the lag it created.