The last version broke the below code that I had in the Wizard Control. I have in the first all PK and FK field for debugging purposes, and the ItemsBO does not create any new record. I don't see the value of -1 when a new record is added.
If I install the previous version then all works fine. I really spend some time to figure out why code that works fine suddenly stopped working.Members->PaymentHeader->Items |Address
In the above the Member is the parent of PaymentHeader and the Address table. There is much more code into it but this line Me.ItemsBO1.Add() does not even provides any error message. While I had a custom properly that failed due to that.
Right now I am working with the previous version.Let me know if you have any idea.
Regards,
Doron
OK I will prepare a sample for this proj.
Dustin, I tested Doron's application, and the last BO is not even creating a blank records, the bo.count is 0. Everything is setup properly and the code works with a previous version of SF and it is only failing with the most recent available.
Any chance to look the files sent to you?
Please find the zip files for the project. In the older project my wizard form works fine and while using the newer version it breaks.
Here is the small project that I used on July 2008: http://www.dfarber.com/HumanFindProjects_Wizard.rar
Here is the database: http://www.dfarber.com/HumanFindAdmin_database.rar
Here are 2 videos:This is the old version from my note book.http://www.dfarber.com/SF_Video1.rar
This is from the desktop computer and has the latest SF. This one shows where it breaks.http://www.dfarber.com/SF_Video2.rar
The form named is called: MainProductSelection
Any chance to review the above?Regards,
You have a number of issues with your code that don't line up. You have NULL values coming in on new records (which you should allow initialization or init them yourself). But the reason your ItemsBO1 shows a 0 is because the relationship between them is wrong (because you are allowing NULLS on the child BO). You had the AllowNullValuesOnNewRow property set to True, which since you are not taking care of the NULLs through BO logic or yourself, it will never work. Set the AllowNullValuesOnNewRow to False on the ItemsBO1 and it will work.