Hi Hilmar,

Good point about local variable "blocking" the public variable. I have already changed the local variable name to loMeta and therefore should be no conflict. Thank you very much for your help.

>I was forgetting the following:
>
>If a public and a local/private variables do have the same name, then, as far as I know, you won't be able to access the public variable. This may defeat the purpose of having a public variable in the first place, although there is of course a chance that you actually don't need it in a specific procedure.
>
>So, once again, I would simply avoid this situation, by giving the local variable a name that starts with "l" for "local". (The public variable should start with "g" for "global", but may be more difficult to change if you already use it in scores of places.)
>
>>Is it a problem if a public and a local variable have the same name and are created from the same class?
>> ...