main logo
Subject: Re: Parent - child BizObj
Author: Mike Devlin
Posted: 2000/11/20 14:41:16
 
View Entire Thread
New Search


<I><FONT COLOR="#663300"><I><FONT COLOR="#663300"><I><FONT COLOR="#663300">Hi Mike,

<I><FONT COLOR="#663300">One Problem, the form now only works properly when I have the data session window open and I have the views in browse mode.</FONT></I>

This makes little or no sense. If anything, the opposite should be true. Having the data session window open or a view open in a Browse window should have no impact in and of itself. However, Codebook controls the active work area. If, in the process of opening up the browse windows, you change the active work area, you could break the code.

Set a breakpoint on the Agreements.oBehavior.Next() statement and find out what is going on.
</FONT></I>Hello again, Pam,
I have been working a few other aspects of this project, but I have finally gotten back and debugged throught he code. One error that is being thrown, is from the cset.set() function. At line 91 (SET &lcSetCommand &lcClauses; "SET EXAC TO [OFF]"), an error is thrown, but it does not stop the flow. My question is, is the error number thrown (10) the VFP error 10 (syntax error)?

</FONT></I>
This does not seem to be the problem right now, although the 'clauses' IF statement in the Cset.set() function seems to need a set of perens.
My problem with the next() function, is that the routine is resetting the DE to the original state. In other words, the pointer is moving back to record number one, then iterating to record two. Without the debugger running, the process happens so fast that it is impossible to notice, and it seems to be hung up on the second record. I am working on tracing down the cause, but I do not think the "set exact to off" error is the problem. Let me know what you think.

</FONT></I>

What I finally came across, was that I had to put the parent bizobj on the form last, so that the select(0), of the form would be the parent view's workarea. I am not sure why the framework was not taking care of this itself, through the parent child properties, but the form now navigates through the records, perfectly.
Devman
mdevlin At ajdebruin .D.OT com

 
©2000 Mike Devlin
<-- Prior Message New Search Next Message -->