Yes, I got the message, but thanks for the additional caution.

Another one of the "interesting" behaviors is jumping to a sub which
consists simply of a Select Case ladder to categorize an entering value and
then return. Stepping through the code, it falls through the ladder, finds
a true rung, executes the line inside the rung, falls to the End, then
immediately jumps back up to the Select Case and starts down the ladder
again. It appears that _cell.value =_ operating on a string like _172:
15.3_ really knocks Excel cross-eyed. Yee-hah.


"Greg Wilson" wrote in message
...
George,

Caution: I don't know if you read my post closely, but I had the same
thing
happen to me where macros in other modules not even related to the macro
being run fired and the worksheet froze. This was a long time ago and I
don't
remember exactly; but I believe this one corrupted immediately after using
CodeCleaner and I could never open it again - i.e. a total write-off !!!.
Obviously it was corrupted before running CodeCleaner but at least I could
open it. My advise is NOT to use CodeCleaner at this point just in case,
but
to first save your code manually and also ensure you have a copy of the wb
before doing anything.

Greg

"G Lykos" wrote:

Thanks, Greg. Reminds me that I saw mention somewhere online about the
Code
Cleaner that also highly recommended it - must be very good, will give
it a
shot.

Regards,
George


"Greg Wilson" wrote in message
...
Sounds like deja-vu all over again to me. The effect you describe
happened
to
me a long time ago and I believe it was just the result of "dirty code
modules". I attributed it to having written and revised too much code
without
using Rob Bovey's CodeCleaner. If I recollect correctly, when I
finally
did
use CodeCleaner, I couldn't open the wb again because it got
corrupted. I
won't blame it on CodeCleaner but I think, if I were you, I'd save the
modules individually manually before using CodeCleaner. I would be
extremely
careful at this point.

Then of course, it could be something to do with the complexities of
Pivot
Tables and not what I describe.

Regards,
Greg

"G Lykos" wrote:

Have run into a crazy problem. Have a macro that scans selected
cells
and,
if the content is a string, does a string manipulation. However,
have
discovered that if the content is a certain type of string, VBA goes
into
orbit.

Essence of situation: Select a series of cells in a pivot table.
Cells
format is General. Execute a loop: For each cell in selection, if
typename(cell.value) = "String" then cell.value = "0" & cell.value.

Typical string data is <533: Then Text. Code works fine to make
this
<0533: Then Text. However, when data is <715: 1.2, cell.value
tests
true
as string, but cell.value = "0" & cell.value causes a cell value of
<0.496541666666667 instead of the intended <0715: 1.2, is still
format
General, typename string, and the worksheet is wacked out and VBA
code
jumps
out of the sub and starts executing in other subs that aren't even
referenced in it. End up having to use Task Manager to kill Excel,
then
start over. So, what in the world is going on??

Win XP Pro, Office XP, both with all updates.

Thanks in advance for any ideas!
George