>Hi Dragan,
>
>I hope you will sleep well - now.

So I did, thanks :)

>How I figure out? This is that I do not use the property window. I have a multi lang app, and lable captions etc. are bound to meta information. So I con not enter a lable in properties window - I need to code like
>

>.lblField1 = _SCREEN.goMeta.GetTextFromMeta(cTable,'Field1')
>.lblField2 = _SCREEN.goMeta.GetTextFromMeta(cTable,'Field2')
>

>A little bit boring to add for all lables, isn't it? So I came to the conclusion that this might be done by code. I create a little prg the generates, depending on ASELOBJ and an string those code. A little bit later I need, for some reasons, to adress it from THISFORM or this,parent.parent.. down to form level. So I thought it easy, going backwards the PARENT object until there is no parent. But I end up on level to much. Tracing my code I figured out that the form has a PARENT - a formset.
>
>BTW.
>Open up a non form class. Try my code. You will see that the class is contained in a form and thisone within the formset.

Incredible.

It seems the only reason I didn't run into this is that I'm drilling for a parent only until its baseclass is what I expect, not while it exists (or "exists"). And most of my drilling is downwarts, i.e. I start from the top and recurse my way down to each member on each level. That'd be the visible top level, not the imaginary top level that VFP serves us :).

>Whats left? Ah what do you mean by
>>...I used aSelObj() ...
>?
>
>If I enter
>

>?ASELOBJ(laO,1)
>*ASELOBJ(laO) will not return the form
>?lao(1,1).parent.baseclass
>

>I still receive "Formset"

Yes, that's what I meant - I got the object reference in a different manner, and it gave the same result as you got.