Jump to content

Bug with unidblookupcombobox - second post


d.bernaert

Recommended Posts

Hello,

I'm still having a problem with unidblookupcombobox when using the mode umNameValue.

I have a unidblookupcombobox filled with customers with the mode umNameValue to be sure that the correct customer is selected.

I also have a trigger on the unidblookupcombobox that allow the user to create a new customer if not present in the list.

When the user clicks the button to create a new customer, he gets a popup where he can create the customer.

When returning, in the callback I refresh the list linked to the unidblookupcombobox to have the new customer included in the list.

When selecting the new customer, I always get index out of bounds.

I don't have it when using mode umNameOnly.

Anybody?

Link to comment
Share on other sites

Normally to solve this kind of problem I point to nil the TDataSource.DataSet property attached to the TUniDBLookupComboBox, refresh the dataset and then point the TDataSource to the actual TDataSet descendant that have the data.

Best Regards

Link to comment
Share on other sites

Hi,

thank you for your answer, but it does not seems to solve the issue.

I've tried with the following code (removed the datasource and the listsource just to be sure) in the callback but I still get index out of bounds.

procedure TQuotesAddFrm.CallBackInsertUpdateAccount(Sender: TComponent; AResult: Integer);
begin
  if CrmAccounts.Active
  then begin
         ComboAccount.DataSource := nil;
         ComboAccount.ListSource := nil;
         CrmAccounts.Refresh;
         ComboAccount.ListSource := DsCrmAccounts;
         ComboAccount.DataSource := DsHeaderWork;
         if UniMainModule.Result_dbAction <> 0
         then UniFinancialModule.HeaderWork.FieldByName('Account').AsInteger := UniMainModule.Result_dbAction;
       end;
end;

Link to comment
Share on other sites

  • 2 weeks later...

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...