Hi chewee,
I took a look at your database and the first problem I see is that your database isn't normalized, meaning that you don't have your tables set up in a way that promotes meaningful relationships. This makes it extremely difficult to troubleshoot because your tables/data aren't technically uniform.
For instance, all of the available products/buyers/reason codes/etc. should be in their own table, along with any descriptions/addresses/phone numbers/etc. that are related to them. These tables should also have a unique ID (typically an autonumber field), also called a primary key, in the table to identify which field belongs to which index.
Then these tables should be setup with relationships using a foreign key in other tables. An example of this would be having the Product primary key (perhaps called ProductPK) in the Products table link to the Product foreign key (perhaps called ProductFK) in the Invoice table.
The reason for doing this reduces the amount of data entry that must be done and makes querying the information a million times easier.
Here's a link to an article written by one of the forum administrators:
Normalisation and Table structures
Check out the link and see about getting your database in order first. Once you take care of that, then it will be much easier to return the data you are looking for because your query will be able to hone in on just the elements that you are looking for much quicker.
If you have any questions after reading the link and trying to alter your database, don't be afraid to ask. This site is full of great people that are more than willing to help and, most importantly, teach you how to be a better database developer.
~beacon
10
