Problem with Multiple entries

[Kasghost]

I am trying to create a DB in Access 2007 where the values in certain fields requires multiple entries.

I would like to send this DB out as an HTML to my techs and have them fill the information in.

The problem I am having is that I am having to create too many tables. I would really like to have no more then 3 or 4 tables.

I've been able to setup most of the tables so that each value has only 1 entry but when I get to the inventory tables that is just impossible.

Below is an example of one of the multi entry tables I would need.

So far I have set this table up as follows

Table Name : Computer Information

Field 1 : Office Number (Primary Key)
Field 2 : Computer Name
Feild 3 : Computer Serial Number

While field 1 would only have a single entry fields 2 and 3 would have between 5 and 30 entries.

While I could use the serial numbers as the key for this table I don't want to have to send tons of emails just to get the info from one office.

If anyone could give me some direction it would be greatly appriciated.

[NeoPa]

Firstly, you should visit (Normalisation and Table structures) to get an understanding of how tables should be laid out and how they should store the data.
Transferring data remotely is another issue entirely.
Sending the whole database backwards and forwards does not sound like much of a solution to me.
I normally create a Back-End database with just the data tables defined and send that one backwards and forwards between the sites.
It is important, in these situations, that the Back-End database is Compacted and zipped up before sending.

[Kasghost]

I read the Normalisation and Table Structures Guide and I understand where I started to go astray with this. Was just hopping someone knew an easier way to set it up for the data collection aspect. Thanks for the advice.

[NeoPa]

Sharing data in this way is not a simple situation.
The best method for you depends heavily on a number of matters, including your experience using Access and the data that you're trying to share.
My solution (outlined in post #2) is what I generally use, but may not be the most appropriate for you.

[Kasghost]

My experiance with Access is vert limitd at best. I took 1 5 week basic class and in it we created a few very simple DB's. What I am trying to accomplish is to create an asset list of all the equipment in each office. What I have done so far is create a DB with 6 tables. In each table I singled out 1 field that is unique to that table as my primary key and included an Office ID field which is the primary key in my first table. But now the problem I have is how to get the values entered into the DB. I have about 2000 offices around the US and I was kinda looking at the Html idea as a way to have my techs enter data and then bring that into the DB. But like I said with 2000 offices and each having 5 to 30 computers it gets really difficult to send that amount of emails and not have something go terribly wrong. I know that what I am trying to do is way out of my league right now but we have to start somewhere so any input is greatly appreciated.

[NeoPa]

Sounds like you've got yourself a pretty big problem there.
How about you start out by posting your table MetaData in the following layout.

Table Name=tblStudent
 Field; Type; IndexInfo
StudentID; Autonumber; PK
Family; String; FK
Name; String
University; String; FK
Mark; Numeric
LastAttendance; Date/Time

[NeoPa]

Actually, HTML is probably a better idea if you can get it to work.
You may want to post a question on this in HTML / CSS

[Kasghost]

Thanks for the help but I think I found the simple solution I needed. I am just going to setup a few workstations with Office on them and have my techs remote in and fill out a spreadsheet for each office and then I can import those into the DB. Has worked so far in my test run.

[NeoPa]

Thanks for replying.
Yes, that was one of the ideas I was thinking of when posting #4 earlier. If that's a way you're comfortable with, then good for you.
If you have any difficulties with it please come back for help :)