Since an item can have many prices, the prices should be in a related table. Also since an item is not unique to a customer (any customer can buy any item) having the customerID in the tblItems is inappropriate. The item table should look like this:
tblItems
-pkItemID primary key, autonumber
-LongItemNo
-txtItemDescription
tblItemPrices
-pkItemPriceID primary key, autonumber
-fkPriceTypeID foreign key to tblPriceTypes
-currPrice
tblPriceTypes (a table to hold the 3 types of prices: regular, sale, cash & carry as records)
-pkPriceTypeID primary key, autonumber
-txtPriceTypeName
Now, I assume that the price type is pertinent to the invoice for a customer, so I think you need to record the invoice
tblInvoice
-pkInvoiceID primary key, autonumber
-fkCustomerID foreign key to tblCustomers
-fkPriceTypeID foreign key to tblPriceTypes (this will determine the price type to be used for this invoice
You do not need to bring in the account number since it is already part of the customer table.
Since a load can have many accounts/invoices, it describes a one-to-many relationship....each driver has a LOAD, with differentes customersaccounts
tblLoads
-pkLoadID primary key, autonumber
-LoadNumber
-dteLoad (date of the load)
-fkEmployeeID foreign key to tblEmployees (this would be the driver)
tblLoadInvoices (the invoices that make up a load)
-pkTransID primary key, autonumber
-fkLoadID foreign key, tblLoads
-fkInvoiceID foreign key to tblInvoice
Can an invoice contain many beer items?
In order to have easy data entry, you have to have the correct table structure. It is the most important part of setting up a relational database.Based on tbltransaction I would like to have a Nice Input fom to make it easy to put data every day