I'm creating a database for a Pizza store as a exercise for school, and am struggling with creating the tables, and what to put in them.

I'm supposed to design a database and focus on the order entry and delivery aspect, the orders can have multiple toppigs per pizza, different prices for different toppings, multiple pizzas per order, and include other non pizza items (such as soda, fries, etc).

I'm thinking of the following tables:

tbl_customer - customer id, name, address, city, state, zip, phone, etc
tbl_order - order id, customer id, order date
tbl_orders_details - ???
tbl_menu - ???
tbl_toppings - ???

but i'm not too sure what they should include.

help?!?!

It sounds like you are on the right track. Keep going and post back when you get stumped. You are not stumped yet. Keep expanding on your ideas and flesh out the tables with more fields and then try and place an order in your head and see what happens.

__________________
(RG for short) aka Allan Bunch MS Access MVP - WinXP Pro, Win7 - acXP, ac07
If your issue is resolved...follow this link for directions on how to use the Solved thread tool!
Teaching is not filling a bucket but lighting a fire. Borrowed quote..."Docendo discimus"

I don't think the order details table is a good idea. Just include a field in tbl_order for any details or specific instructions. The menu and toppings tables are both good. You won't need to call the toppings table unless it is a pizza, obviously. If you're unsure what tbl_menu should have in it, I think it should have every base variation of pizza (like large thick crust, small thin crust), and then those extra things you mentioned like different kinds of pop and fries. Do you have to build an interface?