Lily
If you use a combobox instead of a text field, the user can key in or look
up a part number... or you could have them look up by description, if that's
easier for them to remember.
And if you include the description, price, part number (?and ProductID)
fields in the query that underlies your combobox, you can add the following
to the combobox's AfterUpdate event:
Me.txtDescription = Me.cboProduct.Column(1)
Me.txtPrice = Me.cboProduct.Column(2)
where Column(n) is the n-1 column in the combobox's rowsource (.Column() is
zero-based, start counting at "0").
Your syntax may vary...
By the way, I would suggest that your Description and Price controls are NOT
bound to underlying fields in tables ... there's rarely a good reason to
redundantly store data (you already have it in the ProductDetail table,
right?), and there are many good reasons not to.
--
Regards
Jeff Boyce
Microsoft Office/Access MVP
Microsoft IT Academy Program Mentor
http://microsoftitacademy.com/
Microsoft Registered Partner
https://partner.microsoft.com/