>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).
oObj could be a property of application object - oApp.oObj, or even an element of application array property, isn't it?
oApp.myCoolObjects[n]= NEWOBJECT("something","something")
Nick Neklioudov
Universal Thread Consultant
3 times Microsoft MVP - Visual FoxPro
"I have not failed. I've just found 10,000 ways that don't work." - Thomas Edison