>No, it's gIAmReallyStupidForDoingThisToAVariable
>
>As to object references, I'll bite: If I am doing oObj=NEWOBJECT("something","something") and I am doing this in some method somewhere but want oObj referenced everywhere, what's wrong with PUBLIC oObj? Or do I have my head up my butt? (a common occurence lately).

John,

The problem is that you are creating an object reference is the wrong place. I would either, create the global object in the startup program as private or make the object reference a property of another object that has a global scope (note NOT public but global, which to me means private to the application).