R
Ron Weaver
I am in the process of creating a new database. It makes sense to me now that
everything has to be entered into the Orders table. I am using the Northwind
Database to try and understand the structure. I am in the process now of
adding the combo box to the Orders table with 2 columns: CustomerID and
CustName with 0" for the first column. At least I'm headed in the right
direction now.
Many thanks to you and Al
everything has to be entered into the Orders table. I am using the Northwind
Database to try and understand the structure. I am in the process now of
adding the combo box to the Orders table with 2 columns: CustomerID and
CustName with 0" for the first column. At least I'm headed in the right
direction now.
Many thanks to you and Al
John Vinson said:The CustomerNumber field is a Text field. Here is the recordsource for my
'Orders' form:
SELECT Customer.CustomerID AS Customer_CustomerID, Customer.FirstName,
Customer.LastName, Customer.Address, Customer.City, Customer.State,
Customer.ZipCode, Customer.Phone, Customer.Fax, Orders.OrderID,
Orders.CustomerID AS Orders_CustomerID, Orders.OrderDetailID, Orders.Room,
Orders.TodaysDate, Orders.StartDate, Orders.EndDate, Orders.ArriveTime,
Orders.StartTime, Orders.EndTime, Orders.Notes, Customer.CustomerNumber
FROM (Customer INNER JOIN Orders ON Customer.CustomerID = Orders.CustomerID)
INNER JOIN [Order Details] ON Orders.OrderID = [Order Details].OrderID;
THAT is the problem. Thank you.
I see elsethread that you're reevaluating your table structure. When
you do so, consider using *TWO* forms - one for the customer, one for
the order - since they are different entities with different
requirements! If you base your Orders form *just* on the Orders table,
you can put a combo box bound to Orders.CustomerID displaying the
customer name, and storing the customerID; you can even put VBA code
into that combo's NotInList event to pop open a Customer form so that
you can enter the information for new customers.
John W. Vinson[MVP]