That's a good one! I'll add it to the list for the next class. Didn't think of that. Everyone else: consider that your homework!

I like this thought, can you include an override checkbox?  in case the same person needs several rooms for different events on the same day and time...lest say need two rooms one will be Access Intro  other for Access Expert. or adjoining rooms like hotel.  Mom and dad 1 room, kids get the room next door?  just a thought sounds like a good challenge.

V/r
Juan

Challenge accepted. Sounds like a good project, and a learning experience for all.

Richard & Juan - I like the over ride.  I'm working with over 50 different locations with any where from 1 - 5 "rooms" per location.
That makes it real fun to work through.  Not too terrible though with proper table structure and relationships.
Even more challenging is that each one is available only certain days of the week.  Some are 7 days, some M-W-F, some Tues-Thur-Sat., etc.  I'm glad there is only 7 days in a week!
It's definitely been an interesting project.

More great ideas. :)

Can you do the product planner into this also I lke the birds eye view of a given start date with end date to see whats available at that given time??????
Am I asking to much?

V/r
Juan

I'll do my best. I'll probably release a version 1.0 first and then you guys can tell me what more to add to it after.

Hi Richard
Is there a way to move the reservations to the rental history once the end date has passed?
Cheers
Michelle

Michelle -
One thing Ive learned about Access is any time someone asks "is there a way to do x" they are almost always asking the wrong question. The answer to that one is almost always - Yes.

The better question then becomes "how do I".  You pretty much answered that in the question you asked. LOL

For this time, it would be pretty easy (in my mind any way).  First create a copy of the tables you are wanting to archive the history of  - such as ReservationHistoryT copy the structure only.  Modify the new table change the Id field from Auto Number to Long Integer and add a new Id field that is auto number.  

Then it is just a matter of appending ( "moving" ) the data to the history table and then delete it from the original table.

I see you are a Gold Member as well as in the Developer Level so check out the Don't Delete Data Tech Help.
Richard covers this in detail.
Here is the link:   https://599cd.com/blog/display-article.asp?ID=1410

Just a quick addendum.  
You might be better off to just mark records "Completed" or what ever you choose to call it.
Unless you're getting to large size wise or there is so much data it is just slowing things way down to have the historical data in the same table, reporting etc is much easier not creating a history table.

History and current tables can be joined in the future using a UNION Query BUT fields have to match exactly and require a pretty advanced level of SQL knowledge.  (I'm not quite there yet)  This hasn't been covered yet in depth in the courses other than the SQL Seminar - Which is a MUST in my opinion.
Something to consider...  I'm sure others will chime in.

I love everything Scott just said. :)

H Scott
Thank you and your dead right, stupid question.
I know there is a way, I just don't know how.
I might be in the Developer level but I am certainly not a developer. I just follow along the lessons and sometimes the penny drops. I love Access and Richard's lessons.
I think your right about just marking completed.
I will check out the SQL Seminar, I've got just about all the others.
Thanks again
Michelle

Michelle -

Not a stupid question at all.  I was just trying to get you toward the 'critical thinking' part of working things out.
The extended cut of the Don't Delete video above takes you through the how step by step.

Don't get discouraged just keep on keeping on.  The most valuable lessons (and most satisfying) are the ones where you work through the problem and come up with the solution yourself.  It is those sessions that you also remember the best.

Best
Scott

Hi Scott
I'm certainly not discouraged. Sometimes I do manage to put the leggo blocks together and it feels great.
Cheers
Michelle

It's kinda like how I differentiate between a Quote and an Order in my regular lessons. It's literally just a y/n field. The only time I ever bother using an archive table is if the primary table is getting HUGE and you don't want to lose the old data, but you need to shrink your database size. I keep ALL old customer correspondence in an EmailT however it was getting close to the 2 GB limit, even as a single-table database file. So, I broke it up and I archive all of the old stuff. I almost never have to go back more than a couple of years for an old email.

Thanks Richard, I am just going to have an IsPaid yes/no, which will suit my needs just fine.