>I looked at that code but it's wrapped in an IF statement that prevents the creation of a new key if one already exists. If the business objects New() method is fired the first thing that happens is the table should append a blank; "lnRetVal = this.oBehavior.New()". If the NewID function is part of that table then a key will already be created. In order to get to the line of code "=SETFLDSTATE(lcPrimaryKey, 3)" in the OnNew method something had to fail.
>
>Stonefield was causing my problem because I had overlooked the SDT property "View field property inheritance". So I discovered yesterday that a lot of my views were making double calls to the NewID function.
>
>Thanks,
>Bill

I had that checked in Stonefield too. I unchecked it, added a field to the parent table. This re-gens all the views.

No change in my custid being 1 greater in cust (parent) then in the accnt (child). This is getting very frustrating!

I am wondering if I am going about this the wrong way?

I have a one - many - one environment data names are cust - accnt - soldstk. Pages 1&2 use v_cust, pages 3-6 use v_accnt_stock. On page 3 I am grabbing custid. It has been saved via the standard OK button on the cbizobjmaintenanceform.

This is starting to get irritating.