Assistance with creating tables

[manovice]

I am new to the forum here and am trying to create a database for my work. Here is my data:
We have a unspecified number of facilities (they can be added and dropped at any time)
Each facility will have an unspecified number of visits to them every year (some more, some less)
Each visit will result in the following:
1) A report of the visit
2) (Potential Result) A letter to the facility about the visit
3) An in-house report number for a web-based system (no duplicates)
4) (Potential Result) A letter to headquarters about the visit
5) Another in-house report number if letter goes to headquarters. (no duplicates)

I am thinking that I make a table with facility information like name, address, owner, phone, email, etc. I will have to have an ID autonumber key because some facilities could have the same name.
My issue comes in with if I should split up the remaining information or just put it in one table.

I am envisioning a form that I enter info in to change an establishments information.

Also, another form that will have a drop down or combo box for me to choose which establishment I want to add a visit for and then enter all of the related information and have that info be saved in the one or many tables.

I hope some one can provide me with some assistance.
Please let me know if you need any additional information
Thank you

 

[Premy]

Well, yeah u should create 1 table with facility specific data (AutoNumber Primary Key named FacilityID or something), and another table for the rest, having FacilityID as a Foreign Key. Since some of the data to go into the 2nd table is optional, u might have some blank entries, but it'll still be a solid enough setup.

Your second form could have a main/sub form structure, where the subform is bound to table2 and the mainform to table1.

HTH

 

[olorin]

An Excellent book on database design for helping people starting out with Access is "Grover Park George On Access" by George Hepworth.
Reading that, will explain everything you need to know about designing a relational database.