I would hail anything that fixed a problem
My only guess is that it had something to do with the initialization priority of the objects on the form... the business object is supposed to raise a Navigated event when the form launches to set the initial state of all of those objects. Looks like that wasn't happening, or the handler wasn't attached when it did happen. I dunno; at least it's working for you.
I removed all of the forced navigation, hit F5, opened the form, and it works.
Maybe it is because I just had a Tacquito from 7-Eleven!?! All hail the Tacquito!
Weird. Just plain weird. If anyone has an explanation, I would be happy to field it.
Thanks,Bill
My problem is that the window opens up without the navigation buttons lit up. I can edit/add or delete, but not navigate. If I do click edit, then undo, I have navigation back. If I force the BO to navigate to the end of the collection (MoveLast) via code (FormLoad event), then the navigation buttons show up, but the FIRST record is showing on the screen...not the last...and the details in a list view reflect the LAST record...not the first. This is quite odd. If I then navigate away from the record, everything snaps back into shape and works as expected after that. The workaround is quite simple and acceptable for little 'ole me, but not so acceptable to those nutty QA guys. And, my boss just may mention something about it, too.
Is there a particlar property that I need to look at; or, perhaps I may have done something in my code to make this behavior occur? Any direction on this would be much appreciated!