design Q!

[yessir]

I am starting a new access DB.[

There are 7 sections to the suggested form. They each deal with a different subject pertinent to the form, and there are abot 35-40 fields in total.

The first deals with time complaint recieved and when responded to.

The next is Client info.

The next is Employer info.

The next is Law and hazard info.

The next is Action taken.

Each part has about 5-7 fields. I was thinking that since each part deals with a different "subject" it would be best to have a seperate DB for each section linked by a unique number to be given at time of entry of first part. (UniqueID is an important part to this as well for tracking purposes).

I am wondering if this is a good design plan, or if i should be trying to restrict the number of DB's to later search through as it will eventually be a web application running on machines 28.8kb and up?

My design would have 4 DB's to store entered info.

1) ID, RecievedBy, Date, time, byVoiceMail, callback time, + 2 more
2) Client Fname, Lname, phone, employmentstatus, addr, SIC_code
3) Law, Issue, DescriptionComplaint, location, frequency, duration, immediate, reportedMgmt, Other, Region
4) ActionReq, priority, Action Taken, ReferredTo, Inspection(Y/N), Insp#, InspDate, IfNoY?

 

[Mile-O]

it would be best to have a seperate DB for each section

Why on earth would you want to split something as tiny as that over four databases?

 

[namliam]

He is new and saying DB where he means Table.

Regards

 

[Mile-O]

Just an aside

New? Loads of form questions

 

[yessir]

it's early

It's early and i haven't had a coffee yet, forgive my ineptness at this time, yes i meant to say table, NOT db...

OY

throw me a bone here!

 

[Mile-O]

You are off to a good start but you'll probably find that four tables are nowhere near enough.

Try explaining these tables further - what each field is, what sort of information they hold and how they relate to each other.

What fields will have repeating groups? Take these fields and make new tables out of them. Region, for example, will be a table of its own.

 

[yessir]

yes...

I have already crated tables for the SIC_codes, Regions, Officers, Issues, Hazard duration and frequency, laws, and actions taken, these are to later fill the comboboxes.

The fields are mainly Comboboxes

(recievedby, dates, times, results, addr's, Descriptions, explanition of inspection)

others are comboboxes

(Voicemail (y/n), SIC-Codes, law, issue, hazard freq and duration, officer reffered to, inspected...)

 

[yessir]

I guess

I guess i am just wondering about the main input of info, if the 4 "table" design for the "db" looks ok as given above, or if it should be devided less.