dlookup vs Joined recordsource

[kyledsh]

Hi,

I was wondering, would performance be better using joined recordsource to find related field vs using dlookup?

I have an invoice form and when I select a customer, i want to find the customer address, contact person, and contact telephone of the customer and set it to be the delivery address on the invoice. but i also want the delivery address to be editable without changing the customer's real address.

what i have right now is my form's recordsource is tbl_Customer_invoice joined to tbl_customer_info. then set via vba:

cmb_customer_afterupdate()
txt_delivery_address=me.contact_person & " " & me.contact_Number & " " & me.address

i dont need to use dlookup here because i already have the datas because the tables are already joined in the forms recordsource.



My question is which would have a better performance, my current set up or if my forms's recordsource is just tbl_customer invoice(No joins to tbl_customer_Info) then i just use dlookup?

Ps. i know how to use dlookup

Thanks

[June7]

Domain aggregate functions can be noticeably slow in queries and in textboxes. What you have is probably faster in milliseconds but I suppose every millisecond counts.