Yes, I think I understand why things are working differently in this case.  I just need to set that property to False and it works like I want it to.

When you call Add, the record position is navigated to the new record.  Does this answer your question?

I was searching the properties for something that might affect this and found CheckCurrentRowBeforeNavigate.  When I set this to False my problem goes away, but I don't really understand why I guess.  It seems like it's checking the current row when I set a property not when I call a move, navigate, or seek...

I have a BO which I am calling Add on and then opening a ChildForm to create the new BO.  In the Form_Load of the child the BO is in the Adding EditingState, but when I set the first property on it my CheckRulesOnCurrentRow event fires and causes all of my rows to have errors when the form comes up the first time.  I thought this event only fired on the .Save on the BO.  Why would it be firing in this case?