Ender,
Thank you for your quick response. I've seen your helpful posts all over this forum and am pleased you've taken the time to consider my question.
To use your table naming, giving "Menu Item" a month attribute would not be good design for my case. I repeat menu items several times over the year. Now, I give each item an unique ID and use a separate table to couple the MealID to various months. If I gave my "Meal Info" table a month attribute, I would create much duplication. Without this, I believe the rest of your suggested solution will not work. Am I missing something?
A little more about my business and my database--we produce meals to-go based off of a menu of 15-20 selections that change monthly. I use my "Meal Info" table to track the various meals we offer (generic). I use "Unit Meal" to track individual meals. Unit Meal also serves as a join table to "Order." (There is a many-to-many relationship between "Meal Info" and "Order.")
What I really have is a small manufacturing business. Perhaps I should study sample relational design for a manufacturing process. I just thought I was missing something simple and obvious in trying to use the key "month" to present only the items available for a particular month when entering a new order.
RCB