C
CyberTaz
Not Quite the bug was introduced by the 12.1.2. update which was not
released until 12 August & wasn't available via AutoUpdate [IIRC] until at
least 1-2 days later. Most folks actually have had it applied for no more
than ~35 days.
Unfortunately it isn't usually feasible to issue a singular fix, nor is it
common for any developer to reply "directly" on such issues. It also
fascinates me that many people seem to believe that a bug in a multi-million
line code package can be identified - let alone corrected - the minute the
*symptoms* of that bug are reported.
No doubt about the inconvenience caused, but I would expect to see it
corrected in the next update... And before you ask No, I can't say when
that will be. My *guess* would be prior to the end of October.
Regards |:>)
Bob Jones
[MVP] Office:Mac
released until 12 August & wasn't available via AutoUpdate [IIRC] until at
least 1-2 days later. Most folks actually have had it applied for no more
than ~35 days.
Unfortunately it isn't usually feasible to issue a singular fix, nor is it
common for any developer to reply "directly" on such issues. It also
fascinates me that many people seem to believe that a bug in a multi-million
line code package can be identified - let alone corrected - the minute the
*symptoms* of that bug are reported.
No doubt about the inconvenience caused, but I would expect to see it
corrected in the next update... And before you ask No, I can't say when
that will be. My *guess* would be prior to the end of October.
Regards |:>)
Bob Jones
[MVP] Office:Mac