Trying to figure out the logic: limiting records for lists

[vavroom]

I'm having a hard time figuring out the logic needed to build the
following functionality. I hope some of you will be able to point me
in the right direction.

Creating a small application that lets the user assign a room, a
supervisor, and a topic to an individual for a particular date.

A room can only be assigned for a particular date once. A supervisor
can only be assigned for a date once.

So if we have April 1 as a date, and we assign Room A, and Supervisor
A, neither that room and supervisor are "usable" for April 1.

I need to create a form where the user enters the date, individual's
name and topic then selects a room from a listbox, then the supervisor
also from a listbox. The boxes should be populated only with
"available" rooms/supervisor (based on the date).

Ideally, I want to build lookup tables, one for the rooms, one for the
supervisors.

Where I don't know how to proceed, is how to tie in a particular room
with a particular date, and then build the select statement for the
list, limiting the record to anything that hasn't been selected for
that date already.

Has anyone any idea? (and I realise I wasn't as clear as could be in
my explanations).

Thanks

 

[Van T. Dinh]

Whilt it is possible to do this will a database, it may be more efficient to
use Microsoft Exchange for "scheduling resources". After all. Microsoft
Exchange IS a database underneath but it is built specifically for these
collaborative functions such as appointment booking (with a supervisor) and
resource booking (a room).

Unless, you specifically need to design this as an Access database (and if
your office uses Exchange as the e-mail server), you should check out
Microsoft Exchange and see if this is more suitable for you.

 

[vavroom]

@PC D, thanks for the suggestion, I'll try that out over the Easter
break, just got a pile of papers to process that is litteraly over a
foot high! Won't be able to tinker with the database today.

@Van T Dinh, in this case, we have to use Access rather than rely on
Exchange. What I discuss here is only a small part of a bigger
"system".

@Arno, I've often seen your disclaimer about Steve being a "job
hunter". Frankly, I find it thoroughly useless. Steve provided an
answer to my original question, free of charge. The answer may, or may
not actually solve my problem, but he did come forth with a response.
Please note that I do not know him, work for/with him, or have any
other relationship with him or his business. Fair warning is one
thing, but I cant' help feeling that your systematic posting your
warning in every thread that Steve participates in is a bit of a witch
hunt that, in the end, is more harmful than positive. Just my 2 cents.

 

[John Marshall, MVP]

@Arno, I've often seen your disclaimer about Steve being a "job
hunter". Frankly, I find it thoroughly useless. Steve provided an
answer to my original question, free of charge. The answer may, or may
not actually solve my problem, but he did come forth with a response.

Steve has a poor reputation in the Access newsgroup, but lately he has not
been as
agressive with his misuse of the newsgroups. Part of what Arno is
complaining about is
Steve's tag line that he has thousands of supporters for his behaviour.
Another thing is
Steve posting half or inaccurate answer just so he can get his tag line
promoting his business.

You can see Arno's documentation of Steve's behaviour at
http://home.tiscali.nl/arracom/whoissteve.html

John... Visio MVP