David,

You're right, I don't use public variables neither. My forms add a reference to themselves in a collection obiect at the init and remove the reference in destroy. Whenever I need to acces a form, I use that reference.

My guess was the way I suggested was the easiest for him to do the job. I bet he doesn't need to run multiple instances of that form...

Your point is correct, though, as in many others threads I've seen your messages.


>Christopher,
>
>Sounds like you are using a name dependent object reference. When done from the command window:
>
> do form profile
>
>you actually create a global memvar named profile which holds an object reference to the form. When run from the other form no such memvar is created.
>
>Where are you trying to do something like access profile.SomeObject?
>
>All the code in a form should use the nameless references like this, thisform and this.parent.
>
>Is your listing form trying to access the profile form?
>
>Contrary to what Grigore has suggested you should not use PUBLIC memvars in your application for this sort of thing because it hampers your ability to run multiple instances of forms.
>