It was easy though to make it go back to the normal Font.Bold by adding
this to a normal module, and then deleting it:

Public Type dummy
Bold As Boolean
End Type

Pleased with this as it looked bad.

RBS


"Bob Phillips" wrote in message
...
Bart,

This is just conjecture upon my part, and I have no idea if it is actually
so, and if so where. Like you, I think it is a bug, no proper clean-up
when variables are deleted.

--
---
HTH

Bob


(there's no email, no snail mail, but somewhere should be gmail in my
addy)



"RB Smissaert" wrote in message
...
Thanks Bob, that is reassuring.
This looks like a bug in VBA to me.
Any idea where this could be stored?
The object browser shows (as expected) the normal casing, Bold.

RBS


"Bob Phillips" wrote in message
...
Hi Bart,

I have noticed this many times. Somehow, VBA seems to keep some record
of it, and maintains it looking like a reference to the variable even
when you change/delete that variable. I have never had a problem with
it, even when I have had a variable with the same name as the property.

--
---
HTH

Bob


(there's no email, no snail mail, but somewhere should be gmail in my
addy)



"RB Smissaert" wrote in message
...
Excel 2003.
Noticed something strange and that is that in my code the casing of
Font.Bold is not like that anymore but instead: Font.bOld
Making it Font.Bold doesn't alter anything, it will revert back to
bOld.
I had a look if I maybe had a class or UDT with this property, but I
haven't.
I had a local variable bOld, but changing that to something else made
no difference.
Not sure there is any harm in it, but maybe somebody could explain to
me what is
going on here.

RBS