You are right.... Amy was replying directly to the theme of the old thread
(but the way she worded her message made it sound like the OP following up
to my reply). Okay, so starting a new thread after a user-settable time
interval is not the way to go. Perhaps, then, a "flag" column (like the
Attachments or Watch/Ignore ones) that the user can choose to view (or not)
in which a flag-symbol of some kind would be displayed if the message was
more than a user-settable time interval older than the message it replied to
is the way to go. That way (in this case), I would have been able to see the
flag, which would have warned me that message was a delayed follow-up; then
I would have been alerted to look at the message in the correct way.

Rick


"David Biddulph" <groups [at] biddulph.org.uk wrote in message
...
In this particular case, Amy had actually replied to your previous
message, so her message had the right reference line in the header to be
included in the old thread, but I agree that the problem of identically
named threads being clumped by OE is a pain in the proverbials.
--
David Biddulph

"Rick Rothstein (MVP - VB)" wrote in
message ...
<<Imagine the sound of a hand slapping a forehead rather hard

You pegged it! I completely missed the name shift as well as the date
switch. Whose bright idea in Microsoft was it to append messages in
Outlook Express (and now Windows Mail) onto old, existing grouped message
threads just because they had the same Subject line? Couldn't they have
given us a configurable option to select an "it's too old" time period
after which same-subject messages would become a new thread instead of a
continuation of an old one? Well, anyway, I was completely fooled on this
one... thanks for pointing out the person/date time shift so I could see
what I had missed in Amy's response.

Rick


"David Biddulph" <groups [at] biddulph.org.uk wrote in message
...
The confusion may have arisen in that Amy (to whom you were replying)
was not the OP, but came along to the thread a couple of months later.
The OP (pdberger) had MROUND working, but Amy probably didn't. The OP
was presumably happy with the answers which you and I had given in
September.

My guess is that Amy didn't have the ToolPak enabled, but she may
possibly have suffered from the occasional glitch where Excel forgets
that the ToolPak is supposed to be there. In the latter case, either a
disable/ re-enable ToolPak, or a shutdown/ re-open Excel, or a reboot,
will usually do the trick.
--
David Biddulph

"Rick Rothstein (MVP - VB)" wrote in
message ...
I figured that Add-In had to already be checked given, according to the
OP's original posting, that he used the MROUND function originally and
had gotten a numerical result from having done so.

Rick

"David Biddulph" <groups [at] biddulph.org.uk wrote in message
...
Analysis ToolPak, Rick?
--
David Biddulph

"Rick Rothstein (MVP - VB)" wrote
in message ...
When I tried this I got only "#NAME?"

I'm not sure why you would have gotten that error... the formula I
posted works fine in XL2003 and XL2007.
...