Simpleton alert!

[baba78]

Help!
I have to build a database for work before the week is out and I'm struggling to even get started. I went on an access course but it was a while ago and I wasn't able to really engage at the time as the tutor taught at light speed. I've tried consulting my dummy's guide and another huge book but they don't really make any sense.
Obviously, I don't expect anybody to hold my hand and take me through on a step by step guide to building the thing but i hoped maybe if i could just get started and get the basic grounding done then I'll be away. It doesn't have to be an elaborate beast, just a simple thing for the recording of accidents. I've got as far as creating all my tables (I chose not to give them a primary key?!), but i've no idea how to create relationships or queries - when i try to do either it says i can't do it without already having the other??
Would any kind, pitying or condescending soul be able to help out??

 

[gemma-the-husky]

so why do YOU have to build it, when you have no experience in Access?

and what do you have to do?

 

[baba78]

Because i volunteered, thinking that because what I need to do is fairly basic it might all come quite easily. I'm not completely new to access, I use it a lot but I've never created one before. The elements i struggle with are the building of queries and relationships, that's where i come undone. (I appreciate that this is fundamental).

 

[baba78]

I have to build a database where the details of accidents can be recorded to members of staff. At the front end i just need one single form - like i say, i've created all of the tables i need with all of the information but i can't create a form without queries and relationships...

 

[oumahexi]

You need to decide first what information you want out of which tables, then you can build your queries around the required information. Presumably you will have something like a Staff table: a department table and an accident table. Follow the logic of relationships, for instance, would you expect a member of staff to work for more than one department? If that is the case then the relationship between Staff and department tables will be one staff member many departments (this will most certainly be the case in the relationship between staff and accidents).

Hope this helps

 

[raskew]

Hi -

How 'bout telling us about your table structure(s). Your decision not to use primary keys could be a major problem.

Bob

 

[baba78]

Thanks for the replies.
The decision to not have primary keys was not calculated by any means. I just excluded it because i couldn't understand it.
Is it possible to add primary keys after the fact or would i need to recreate the tables all over again?

 

[raskew]

Tell us about your table structure(s).

Bob

 

[DCrake]

Like any normal business you should already have an accident book that is currently in use. Yeah, Well ask if you can have a look at it and use this as a matrix for your application. Look at what pieces of information is being collected. What is repetative (these will become lookup tables) What is personal to the person. Ask them also what they want the system to give them in the way of analysis. Ie number and types of accidents in a given period. Make a list, try do do this before asking them though. So that when you approach your bosses they will see that you certainly know what you are doing and also you can blag out more time to complete it as it will need developing and testing. Use actual accidents as sample data when attempting to record an accident.

Have the facility to be able to bring up a previously entered accident. Tell them that although this is a prototype the finished article will have a login screen that is password protected (Data Protection Act). When you have completed the data capture screen you will need to think about validation of data, Garbage In Garbage Out.

Finally there is the question of documentation. All apps should be well documented not only from a users poiint of view but as a support document for the application code itself. This will help you and other who may need to visit the source in the future.

Prior to all this I recommend that you familiarise yourself with the following

Normalisation
Naming Conventions
Reseved words

Finally, to say that you have only been given a week to complete this is a bit tight, after considering all of what I have metioned earlier. Any way best of loook and keep us up to date with your progress and ask if you get stuck.

David

 

[baba78]

The tables i have created range from accident types and causes to managers to the name of the contractor company and the rest of it. I've created on big one with all of the elements in a design view, now i guiess i need to create relationships between these and the big one but i don't know how to draw the lines between the two....

 

[Rabbie]

You really will need to have proper keys in your tables.

these links may help to give you and idea of where to start.

http://www.deeptraining.com/litwin/dbdesign/FundamentalsOfRelationalDatabaseDesign.aspx

http://www.datamodel.org/NormalizationRules.html

http://allenbrowne.com/casu-01.html

http://allenbrowne.com/casu-22.html

http://office.microsoft.com/en-us/access/HA012139541033.aspx

Good luck

 

[Dennisk]

I ALWAYS budget 3 months for an Access database.