On Monday 10 November 2008 08:59:17 am Ed Leafe wrote: > On Nov 10, 2008, at 10:50 AM, johnf wrote: > > On my form I have two bizobj's a parent and child. The parent holds > > the > > customer record and the child holds customer notes. 99% of the time > > I do > > don't have a need for a customer note. So there is no need to > > create a > > record in the child table on parent.new(). Therefore, I would not > > set the > > properties NewRecordOnNewParent for the child and > > NewChildOnNew for the parent. Recall I don't need notes 99% of the > > time. > > > > However, on the form I still display the editbox for the child notes > > field. > > The user types in a some text and expects that the notes will be > > saved. Does > > it make sense that Dabo would realize that a record is required to > > save the > > notes and insert a record into the child table? > > I would create the child record; if the user enters text, it will be > saved. Just make sure you didn't switch SaveNewUnchanged for the child > bizobj to True, and all empty child records will never be created in > the database. Remember, creating a new record in your app doesn't add > anything to the database until you save. > > > -- Ed Leafe
I like the thinking - thanks. But doesn't the fk_key get populated from the self.FillLinkFromParent = True and therefore Dabo will see it as a change and save the child record? -- John Fabiani _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/[EMAIL PROTECTED]
