BTW, a quick look at your customer table indicates that you have a structural issue that should be addressed. You essentially repeat a number of fields depending on whether the address applies to the invoice, delivery or order. Since a company can have 3 of these addresses, it is describing a one(customer)-to-many(addresses) relationship which should be handled with a separate table
tblCustomerAddresses
-pkCustomerAddID primary key, autonumber
-fkCustomerID foreign key to tblCustomers
-fkActivityTypeID foreign key to tblActivityTypes (use this field to identify the type of activity: order, invoice or delivery)
-Addr1
-Addr2
-State
-City
etc.
tblActivityTypes (3 records: order, invoice, delivery)
-pkActivityTypeID primary key, autonumber
-txtActivityType
Since you have many contact people at the customer which also depend on the activity (order, delivery, invoice), that would follow the same approach (i.e. a separate but related table).
tblCustomerContacts
-pkCustomerContactID primary key, autonumber
-fkActivityTypeID foreign key to tblActivityTypes
-FName
-LName
The above structure assumes that the contact person is not necessarily associated with a particular customer location/address (your actual application may be different).
Also, there should be no order or quote number reference fields in tblProducts. The fields in tblProducts should only be relevant to the product.