Question Noob

[upeenarce]

hi all,

Here is the point where I have to sound like a complete idiot. I really need someones help - any help is appreciated, SERIOUSLY, anything!

I'm trying to create a database (my first one in about 10 years). In my head it should be simple, but nothing seems simple anymore, especially with the ribbon :banghead:.

My database is something similar to what a hotel would use. The only exception is i don't need it to do anything around prices at all.

All I need it to do, is store what customer is in what accommodation. Then I'd like it to tell me when there leaving and arriving. Ideally a report i can print off in advance.

For the last week i have sat and read as much sample databases as i can and tutorials. But I'm still getting no where with it. does anyone have any suggestions. Or even an old template that they think i could use.

Any Help is seriously appreciated!

Chris

 

[llkhoutx]

I would would define my tables first, then use the form(s) to enter/edit/delete that data.

 

[upeenarce]

Hay,

at the minute thats what i have been trying to do. i have set up my tables as follows:

Customer:
ID
name
ref
nationality
adults (no of)
kids (ages)
special requests / notes

Accommodation:
id
emplacement number / room number
type
code
no of beds
in use by
available

bookings:
date of arrival
date of departure
special requests
no of nights
customer id

so now i have my tables i need them all to interlink (hope thats the right word). Ideally i would like to be able to book some one in and then have the database prevent me from booking someone else in to the same room, whilst they are there.

its the whole part about definig relationships that im having trouble with. Any ideas?

 

[llkhoutx]

Customer:
CustID
name
ref
nationality
adults (no of)
kids (ages)
special requests / notes

Accommodation:
AccmID
emplacement number / room number
type
code
no of beds
in use by
available

bookings:
BookID
date of arrival
date of departure
special requests
no of nights
CustID
AccmID

Never use spaces if field/control name, it drammatically complicates coding.

Revisit you table design, it's very weak. Draw a picture of it and the various relationships.

 

[upeenarce]

Hi, thanks again for the advice.

The problem I have at the moment is i don't quite understand the whole relationship side of the database.

My table naming was sort of worked out from another tutorial i was trying to follow, but adapting it to my own needs.

Does anyone have a good tutorial where i could learn it from?

 

[llkhoutx]

Get yourself a copy of

Access Database Design & Programming (3rd Edition) by Steven Roman (Jan 14, 2002)

It's a terrific book. I use it as a desktop reference.

It's available on Amazon.com for a varieyt of new and used prices.