>>Hi Arto,
>>
>>I looked around (and sent a message to Calvin and didn't get a response) also, and found nothing.
>>
>>Are you working at converting the settings for use elsewhere? If you only need to do it on a onetime basis, you could instantiate the object and read the values off the members, I think. Store it in a db, and you'll have them for generating the values on your .Net or whatever form, mapping to the .Net properties you want to use.
>>
>>For a large app, it's easy enough to rig a setup that pops the form up based on what's in a directory, or what's in a list you feed it, etc.
>>
>>Hank
>
>Seems that there are some insuperable obstacles with instantiating:
>
> do form Form.scx name oTest noshow
> oTest.SomeOleControl

Or, in command window...

modify form myform
aselobj(aa,1)
ox=aa[1]
?ox.someOleControl. ...

or even use amembers(amm, ox.someOleControl,3) (or whatever is the appropriate set of 3rd and 4th parameters). This way you don't get the runtime properties, but then the code which would set them is in plain text anyway, which you can access already.