Car rental - relationships guidance

[ipwn]

I was jsut wondering if you guys could offer some guidance towards thsi car rental project I'm doing.

So far I have come up with these tables.

There is something about them thast not quite right, but I can't really pic up on it, I'm fairly new to Access.

The main thing about this car rental database is not only will it have the booking things, but it will also have the car history in there aswell. So if there is a service or pads get changed then it will be on the database.

I'm not quite sure how to go about making the booking process etc. Has anyone got any useful websites that may be able to help me with this ?

Thanks

 

[brickelldb]

create forms with append queries. figure out what unique identifier will help link it all together (vin #). not sure exactly what you're asking? it seems like your asking how to pretty much DO IT????

 

[ipwn]

Im more after an opinion on the tables really.

Plan on making the database itself myself

 

[wiklendt]

several boo boo's...

what's wrong with your picture is that your relationships don't seem to actually exist. if you had relationships made, there would have been lines connecting each table in this relationship view. Access does NOT create relationships between two tables JUST BECAUSE you name the fields the same, you actually have to physically TELL access that this field Service ID in tbl Service is taken from Service ID in tbl Service ID (you do this in table design view by selecting the field type as "lookup wizard", then following the prompts to reference the Service ID.

the other MMMMMAAAAAAAAJJJOORR problem with this image is your naming convention (never never never never use spaces in table names or field names), and it also does NOT look like a normalised database.... your Service ID looks odd - you should have just one tblService, with a field in it called ServiceID. there should NOT be another table called "tbl Service ID"... and you will DEFINITELY become confused down the track between Service ID and Service Work ID.

i would rename your tables without spaces: as "tblService", and also fields without spaces: e.g., "ServiceID".

you should also NOT have TWO "Car Booking ID" as a primary key in two different tables. if this is a junction table, it should have appropriately names fields to say such, for e.g., "CarReturnID" as PK in your return table, and linked via lookup wizard in your booking table (with THAT field called CarReturnID as a FK)

you seem to be confused about data normalisation. you will need to read up on this - there are HEAPS of discussions about this on these forums: just search for "normalization", you'll find lots.