Hello. You said: "store the value in the Customer ID field in the contact form" . But does not ACCESS store that value from the Combo box (the Customer ID) in the Contact ID field in the Contact Table? And the Customer ID field in the form takes it from there? Otherwise this would no longer work when you delete the field a few minutes later.
Sorry for asking this. New to ACCESS. But paid so much money for lessons from you so that I thought I wonna be sure if I do think it the wrong way...
Thanks a ton from Bonn Thorsten
Joe Holland
@Reply 3 months ago
No. The CustomerID is not stored in the ContactID field of the contact table. The ContactID is a unique identifier for each record in the Contact table. The CustomerID is an identifier for which customer relates to each contact record. You need the ContactID and the CustomerID in the Contact table for the relationship to work. The combo box helps you more easily select the CustomerID for each contact record and stores it in the CustomerID field in the Contact table. Tables hold data and forms display the data.
He (not me! ) said: stores the value in the Customer Id field n the contact FORM.
Anyway: thanks!
Joe Holland
@Reply 3 months ago
He did and it does. The combobox helps you select a customerID for the current contact record. This is saved in the customerID field of the contact table. The form is based on the Contact table.
Thorsten WiedemannOP
@Reply 3 months ago
Hello,
Sorry. But if it would do straight (like it sounds for me) the form would no longer work as soon as he deleted the field. So you gave me the answer I was looking for: it is stored in the table and the form field picks the information from the table.
Thanks
Sorry, only students may add comments.
Click here for more
information on how you can set up an account.
If you are a Visitor, go ahead and post your reply as a
new comment, and we'll move it here for you
once it's approved. Be sure to use the same name and email address.
This thread is now CLOSED. If you wish to comment, start a NEW discussion in
Access Expert 1.