Command Button Not Executing

  • Thread starter Thread starter HankL
  • Start date Start date
Followed your instructions and it works like a champ.
I thought that if I selected the check box in the Form view on various
records all I had to do was select the uncheck button and they would all be
gone.
I guess I am just not sophisticated enough to grasp the entire picture.

What else could I do to take advance of the power of Access to improve on
this database?
And please do not let me forget to tell you how much I appreciate your
patience and working with me to get this issue resolved.
I cannot thank you enough.

Maybe I should put this database available for others to use. This was my
first project of putting it together. I have one for Hotel/Motels
reservations as well.
Many many thanks!!!!

HankL
 
HankL,

Glad to help!

When I took a look at your database, I see that you are keeping everything
in one table. This would be considered a flat file, more like an Excel
file. To use Access a relational file your table set-up should look more
like this:

tblRestaurants
rRestaurantID (Primary Key [PK])
Restaurant
rAddress
etc..
rCuisineID (Foreign Key [FK])
rAveragePriceID (FK)
rReservatiosRequired (Yes/No)
rAttireID (FK)
rRatingID (FK)
etc...

tblCuisine
cCuisineID (PK)
cCuisine (Mexican, American, Indian, etc...)

tblMealsServed
msMealsServedID (PK)
msMealsServed (Dinner, Lunch, Breakfast, Happy Hour, All, etc...)

tblRestaurantMeals
rmRestaurantID (FK)
rmMealsServedID (FK)

tblAveragePrice
apAveragePriceID (PK)
apAveragePrice

tblAttire
aAttireID (PK)
aAttire (Casual, Dress, etc...)

tblRating
rRatingID (PK)
rRating (Excellent, Fair, etc...)

tblRestaurantReservations
rrRestaurantReservationID (PK)
rrRestaurantID (FK)
rrDateReservedFor
rrSpokeWith
rrTimeReservedFor
rrHotelID (FK)
rrCallToConfirm
rrCanceled (Yes/No)
rrHowMany

tblHotels
hHotelID
hHotel
hPhoneNumber
etc...

It looks like you want to take reservations and your way you will have the
same Restaurant in the table many times. What you want is one Restaurant
with many reservations. You also want tables for you combo box, makes it
easier to add values without going into design mode and add to a Value List.

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm
 
tblRestaurants
rRestaurantID (Primary Key [PK])
Restaurant
rAddress
etc..
rCuisineID (Foreign Key [FK])
rAveragePriceID (FK)
rReservatiosRequired (Yes/No)
rAttireID (FK)
rRatingID (FK)
etc...

tblCuisine
cCuisineID (PK)
cCuisine (Mexican, American, Indian, etc...)
Click to expand...

Excellent (as usual), Gina, but this would still cause problems: one of my
favorite restaurants, long since closed alas!, was in Taos, New Mexico: it
served both Northern New Mexico traditional food (enchiladas, red and green
chile, etc.) and New York kosher "milchig" deli food (blintzes, etc.)

You may want a many to many relationship table linking restaurants and
cuisines.

But I absolutely agree with you, that the OP should certainly go beyond having
just one big table!
 
John,

Hmmm, I see your point a *joiner* table for Cuisine might also be in order!

Thanks!
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

John W. Vinson said:
tblRestaurants
rRestaurantID (Primary Key [PK])
Restaurant
rAddress
etc..
rCuisineID (Foreign Key [FK])
rAveragePriceID (FK)
rReservatiosRequired (Yes/No)
rAttireID (FK)
rRatingID (FK)
etc...

tblCuisine
cCuisineID (PK)
cCuisine (Mexican, American, Indian, etc...)
Click to expand...

Excellent (as usual), Gina, but this would still cause problems: one of my
favorite restaurants, long since closed alas!, was in Taos, New Mexico: it
served both Northern New Mexico traditional food (enchiladas, red and
green
chile, etc.) and New York kosher "milchig" deli food (blintzes, etc.)

You may want a many to many relationship table linking restaurants and
cuisines.

But I absolutely agree with you, that the OP should certainly go beyond
having
just one big table!
Click to expand...
 
Back
Top