HELP! Adding multiple combo boxes from different tables

[iain9996]

Hi, please help me!

i am making a database for my own restaurant. To make it easier for my
staff, i am creating a database which allows the users to input the food
orders.

However, i have hit numerous problems. I am a complete amature at access. I
need to add numberous combo box (food) entries from different tables. I then
need to add them together, and display it on a report.

Please help me!

Iain9996

 

[John W. Vinson]

Hi, please help me!

i am making a database for my own restaurant. To make it easier for my
staff, i am creating a database which allows the users to input the food
orders.

However, i have hit numerous problems. I am a complete amature at access. I
need to add numberous combo box (food) entries from different tables. I then
need to add them together, and display it on a report.

Please help me!

Iain9996

It all starts with the Tables. If you're starting with combo boxes, you're
like a cook worrying about presentation before purchasing the ingredients!

You need ONE table of menu items; a different table of orders - probably a
fairly complex application before you get done. What tables do you have now?
Are you planning to enter orders directly in tables (a BAD idea) or to use a
Form for the order, with a Subform for the items (much better)?

 

[iain9996]

hi, thanks for helping!

i am using a data entry form. however, the food order is seperated into 3
tables; Starts, Main course, and side-orders. This is to cut down on the size
of the combo box, because there is around 120 different foods on the menu.

I have given all the foods a 'dish number' and linked them in a relationship.

If this is a bad way of doing it, please just say! haha

Many thanks

Iain

 

[John W. Vinson]

hi, thanks for helping!

i am using a data entry form. however, the food order is seperated into 3
tables; Starts, Main course, and side-orders. This is to cut down on the size
of the combo box, because there is around 120 different foods on the menu.

I have given all the foods a 'dish number' and linked them in a relationship.

If this is a bad way of doing it, please just say! haha

Well, it's certainly not *necessary* and it can lead to a long term
maintenance nightmare. You should instead have one Dishes table with fields
like:

DishNumber <number or short text Primary Key - NOT an Autonumber>
DishName <text>
Category <e.g. Starts, Main dish, Side, Dessert, Breakfast, ...>

Your Form could then have TWO combo boxes, one to pick the category, and a
second combo box based on a query selecting those dishes in that category. The
RowSource of the second combo would have a criterion like

=Forms!YourFormName!FirstComboName

and you would have one line of code or macro in the first combo's AfterUpdate
event to update the second combo.