I have created a SF Maintenance form that maintains a table. The form does have combo boxes on it that use other BO's. All that works fine. I have 12 rows of data in the main table.
The issue is that when run the form, and try to navigate using the toolstrip navigator, it stops after navigating to the second record and no longer allows navigation through the rest of the record set (which via debugger, and Browse, all 12 rows DO exist in the BO). When I then try to close the form, it has set the main BO to isDirty even though no editing has taken place bythe user (form).
The first 3 columns of the table comprise the PK and ALL columns on the BO are now set to "Return Alternate on Null" with a value. 3 columns on the table allow nulls, and are null in the database table. I was able to add all 12 records using the SF form created.
I do have 1 column that does not allow null, that is programatically set, which is the "date added". And the only way I could get it to work was to set the "Return Alternate on Null" property in the BO Mapper.
I know this has something to do with the combination of the database table allowing nulls, and the BO setting of "Don't Allow Nulls", "Return Alternate on Null", "Return Alternate on Null / Set Alternate on Null". It seems like I have yet to find the combination that works.
??????????????