Arg81
Well-known member
from a search, the first row that comes back always displays the wrong data for the customer contact, until I navigate forward one and back one - the contact ComboBox shows the first person in the list, and doesn't show the one it should be bound to.
From testing with my employee ComboBoxes, I see that if I do it in this order;
me.LoadEmployee() 'fills the employee table
me.LoadDetails() 'fills the main table
will show the correct employee name in the combo box. However, changing it so;
me.LoadDetails() 'fills the main table
me.LoadEmployee() 'fills the employee table
Then the first employee in the list is shown in the combobox until I navigate away from the record and back.
However...I can't do this with my customer loading. I iterate through the parent table to only load the "needed" customers, customer sites and customer contacts, so I can't place me.LoadCustomers() before me.LoadDetails().
Is this a damn bug in VS? I remember having issues with it in my old VS2003 app, and I knew there was a valid reason why I started to use global dataSets....
Any help much appriciated
From testing with my employee ComboBoxes, I see that if I do it in this order;
me.LoadEmployee() 'fills the employee table
me.LoadDetails() 'fills the main table
will show the correct employee name in the combo box. However, changing it so;
me.LoadDetails() 'fills the main table
me.LoadEmployee() 'fills the employee table
Then the first employee in the list is shown in the combobox until I navigate away from the record and back.
However...I can't do this with my customer loading. I iterate through the parent table to only load the "needed" customers, customer sites and customer contacts, so I can't place me.LoadCustomers() before me.LoadDetails().
Is this a damn bug in VS? I remember having issues with it in my old VS2003 app, and I knew there was a valid reason why I started to use global dataSets....
Any help much appriciated