Ed Leafe wrote: > On Mar 11, 2008, at 11:30 PM, Paul M¢Nett wrote: > >>> Have you stepped through the code at all? This will give you a >>> better >>> idea of where things are not working as expected. >> As I said earlier, I haven't done any testing other than figuring out >> what revision broke it. I intend to do such testing, but right now I'm >> focusing on getting the updated application delivered. > > > OK, fair enough. But knowing *what* isn't working (i.e., parent > links, memento setting, default values) in the various child records > would be a big help.
I had a few minutes just now, and even though I haven't really stepped through code yet, here's a bit more info: I have code in the bizOpenings.afterNew hook that calls bizSubopenings.new() to add one or more records to the new bizOpenings record. Pre-revision 3925, the new subopening record(s) get attached to the new opening record. Post-revision 3925, the new subopening record(s) get attached to the prior opening record, even though bizOpenings.RowCount reports the row number of the newly added record. All the default values and parent links seem to be filled correctly in the new subopening record, but the problem seems to be that the record is getting added to the wrong child cursor. I have to get some sleep now, but thought I'd share the new information. I'll try to make time tomorrow to make a test case. Paul _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev Searchable Archives: http://leafe.com/archives/search/dabo-dev This message: http://leafe.com/archives/byMID/dabo-dev/[EMAIL PROTECTED]
