|
 |
And lo On Mon, 14 Feb 2011 16:13:24 -0000, bart <bar### [at] home org> did spake
thusly:
> On 02/14/2011 11:08 AM, Phil Cook v2 wrote:
> >As an aside I'd use a "Worksheet_Change" on the sheet itself
> Yes, it seems more practical, especially in case of many worksheets.
>
> >and "If Not Intersect(Target, Range("B:B")) Is Nothing Then" and
> "Source.Formula"
> >to maintain the added value.
> Yes, as I said, it's a start that could be extended to fit one's needs.
>
> >Good that you remembered "Application.EnableEvents = False" otherwise
> >the scripted change will trigger the script again
> >and it's infinite loop time; so easy to forget
> That's exactly what happened with the first try ;)
>
> There are many ways of doing things in Excel,
Oh hell yeah; I wasn't offering negative criticism. The problem is that
when anyone offers a solution it can be slavish followed without an
understanding of how it works; then it mutates to fit a situation rather
than reworked. Offer a different approach and hopefully people might take
a closer look and ask "What's the difference?" :-)
> I wander
> what is the real reason behind the original question,
> since it looks like a minimal example.
> As possible application I could think of, say
> - some kind of non-trivial custom auto-correction;
> - instant conversion of typed formula to value;
> - some tricky content-based auto-format...
As mentioned the normal case would be putting A+B into the next cell. It
would be possible to hide the entire B column when printing if that was
the sole purpose; but I think a PivotTable provides the most customisation
without getting too deep into VBA.
--
Phil Cook
--
I once tried to be apathetic, but I just couldn't be bothered
http://flipc.blogspot.com
Post a reply to this message
|
|
