Hi Quinn,

Something you might want to try this:
Rather than trying to access the form by object name, pass a reference of Form A to Form B's init:

*--Form A Init

DO FORMB WITH this

or if you use classes:

loFormB = CREATEOBJECT("FormB",this)

In form B you could create a property called oFormA to which you can attach the reference passed in the Init

This will also help in situations where you may have multiple instances of FormA and FormB instantiated at the same time, which causes the form object names to be adjusted (FormA1, FormA2, FormB1, FormB2)

Rick

>Jason
>
>Thanks for your response
>
>I tried having a procedure call both formA(Maps) and FormB(Coverages) independently from a menu call. This did clean up one other problem. The problem of the class on the second form not recognizing the occurance of the first form still exists. From inside the code in the class on the secong form (Coverages) I use:
>
>called from coverages.coverprop1.populate()
>
>maps.map1.layers.add (I get an error that maps does not exist)
>
>Is it normal for a class on a form not being able to see another form that already exists? I can refer to formA(Maps) from the init of formB(Coverages)