I really don't want to control it so I will play with it some more and see if I can isolate that it is this control giving me the wierd results.  Is there a way to default the datetimepicker to the current date? TIA.

Since the control is bound to the field on the business object, it is going to pull its value from the business object, so the best way to default it to the current date will be to set the field on the business object in the SetDefaultValues method to todays date.  DateTime.Now will work, or if you don't want the time, then DateTime.Now.Date.

OK, Thanks that is what I needed. I will try that and report back. I still believe this timedate field is what is screwing up the dirty record. I will keep at it...

This gets more bizarre by the minute. I put the code in the setdefaultvalues event and that works but now when I create a new person I get a negative number for the PK which I know I should (I just show the PK as read only), I can fill in the first name and last name and when I put the first character of the address field it automatically fills in the form with information (even the first and last name) from the last person I added and truncates parts of the name. Now I am really dorked up in terms of what to do and how could that happen??????? TIA......

Looks like there is some sort of handler on the address field which is causing it to Navigate the record.  If all of the data is changing to a different record, then the business object is definitly navigating.  Put a handler on the business object's Navigating event and put a break point on that handler... when the handler fires, post the stack trace (along with all the extra stuff that shows when you turn off the "Just My Code" stuff mentioned above.

Every Field after the First and Last name fields causes the other fields to fill with the info from the last person added. How can that possibly be? I have not tried your suggestion yet but I was just seeing if it was only one field that caused the form to autofill and found out it was not. This is more of frustration note more then anything else at this moment. I will try your suggestion and get back. TIA.

I tried your suggestion about putting a break point in the navigating event of the BO. It is not fired because the break point does not fire. I have inserted a picture of what the form looks like and when I took this snap shot it was right after I entered the 1 in the address 1 text box. Any suggestions would be appreciated. TIA.

I can practically guarantee that you have an event that is being handled causing either the row to be set back to the previous row or causing some type of validation issue.  If you place a breakpoint in the Set of the BO property, you may then be able to see at what point the values are being set or updated....also, the Navigated and Navigating events will definitely be firing...so if they are not firing then you may have your breakpoint in the wrong place.  Be sure to put your breakpoint in the Navigating of your BO (you may want to add some code in there so you can set your breakpoint).

I put the following two lines in the navigating event of the BO with a break point on the second line. The break point never fired.

dimension xcnt  as integer

xcnt = 1

I will try the Set event and see what happens. TIA.....

I think that there is something fishy going on with your form (as I think that you already knew ).  If you create a new form, drop on the BO and a few of these fields, do you have the same behavior?  You need to determine if the issue is within the form or the BO itself...this would be one way to find out.