>Good one Jay!
>
>I got it now. I didn't realize that objects had scope considerations the same as variables. After I added the PUBLIC oObjectname to my form(s), everything worked error-free. That was the missing link!
>
>I guess the way I am using VFP is kinda like FoxPro for DOS which is why I don't get exposed to things like OOP very often. It's not by choice. It's because the people I work with/for like it that way. Hmmmmmmmmmm.
>
>I appreciate your clearing that up for me. I had just reviewed and re-read asection on scoping variables in a chapter in one of my many VFP books. But I still didn't see anything about scoping and objects. Now what I am doing makes sense. I feel better now. That wasn't so bad, now was it.
>
>Thanks very much. I printed your message for future reference.

Hi Steve,

May be I understood you literaly, but did you really declare public variable (say, in form's init)? No need to. Create a form property, say, oTable, then you can do:

scatter name thisform.oTable memo This way you would use form's property instead of public vars.

Initialize this variable to null in Init and in destroy do the same.