Gees Louise. All she wants to do is track what countries her clients are
from...

She's not running Fort Knox.

"Craig Alexander Morrison" wrote in
message ...
Been here since 1994 when it was MSACCESS, probably answered ten of
thousands of questions, admittedly not so much in recent years.

And your point to that is what... please don't correct you when you are
wrong?

Is the database not there to prevent data inconsistency is that what you
are inferring?

Is it impractical to ensure data consistency?

Indeed the DATABASE should prevent not only the desk clerk from entering a
duplicate room number it should also prevent the APPLICATION(S) from doing
so too.

The original questioner is going to be running a business on this
database, it is not some toy example, do you think you should be a bit
more concerned about data integrity?

--
Slainte

Craig Alexander Morrison
Crawbridge Data (Scotland) Limited

"Amy Blankenship" wrote in message
...

"Craig Alexander Morrison" wrote in
message ...
In the real world, once the rooms have all been entered, most people
stop.

The database is there to maintain data integrity, not the desk clerk,
what if one person entered a room twice?

Why would desk clerks be entering room numbers? Presumably this an
initial setup thing that wouldn't ever need to be touched again unless
the hotel expanded or for some reason the room numbers changed.

Do you ever answer posts yourself, or is your sole purpose on this board
to try to impress people with your theoretical knowledge by putting down
the posts of people who do?

-Amy