<I><FONT COLOR="#663300">Hi Mike,
<I><FONT COLOR="#663300">On the second pass, the debugger shows the current alias() as being the child view, which is at recno() 1 since it is empty, which also means that eof() returns .T.</FONT></I>
It sounds as though you might have your child bizobj registered with your form as the primary bizobj. I can't think of anything else that would cause such behavior.
</FONT></I>
Hello again Pam,
I thought about that, and checked all the properties again, but all of the properties seem to be in order, as you helped me with earlier.
I was tracing the code from the next.click() to see what was happening. That is where I saw the focus remaining with the child view (alias() = child view in watch window).
Now, I traced the code from the bizobjform.init(). The parent seems to go through fine. And the child seems to go through fine. The reference collection adds are a bit confusing, since all the objects are calling it when adding objects (the bizobj's, the DE's, the bizobjform, etc). I stepped through and watched the oRefBizObj.add() and I did not see anything that would indicate the child as a child. I do see a routine in the bizobj.init() which seems to register the bizobj as a parent, which neither bizobj went through, since lnoautoparent = .T.. I am wondering where the registerchildbizobj() should be called.
Thisform.registerbizobj(this) is called after both bizobj's, and the reference collection.add() adds both bizobj's to the array, so that this.achildren[1, 1-4 parentbizobj info]
this.achildren[2, 1-4 child bizobj info].
So now they are both registered to the form, but I do not see one being registered differently than the other. I know I am missing something, I just cannot seem to find it, or is that redundant. =)
Devman
mdevlin AT ajdebruin DO.T com
©2000 Mike Devlin |
