Modular Table??

[Brambojr]

I am working on a database that I am trying very hard to keep modular. The goal is to make it very easy to use even for the non-database minded. Problem? This is for a distribution center and one table is for equipment types (and those alone) another table records wether or not a person is liscensed for the different equipment types. I know at some point we will add new forms of equipment but want to make the addition of them very seemless. Is this in anyway possible?? I am now well versed enough to read VBA and know what is happening. How do I add this new equipment without having to go into the databse itself?? Brambojr

 

[gwinn7]

Why not use a combo box on your entry form for selecting existing equipment, then place a command button next to it called 'Add New'. Then, if the user needs to add an item, then clicking 'Add New' will launch a form that will allow the user to enter a new equipment item. After the user saves and closes the form, the combo box list refreshes making the new option available.

Gary
gwinn7

 

[Brambojr]

maybe I am missing a point here, but right now I have a column in a table for each vehicle/equipment type (Yes/No). If another vehicle is added I then would have to add another column, or is there a better way??? Brambojr

 

[JerryDennison]

You should not have separate fields in your table for equipment. i.e. you should not have a field whose name is the name of the piece of equipment. You should have a table where you enter a record for each piece of equipment in the table. You would then have another table that is linked to this table and then either the individual to define authorized use or a table of groups that an individual may belong to that is authorized to use the piece of equipment.

In other words, your structure is fundamentally wrong and does not adhere to the First Normal Form(all attributes must be atomic).

 

[gwinn7]

Exactly!

You need to build the building before you put things in it!

Gary
gwinn7

 

[MichaelRed]

Brambojr,

You need to get a text/reference manual re relational database design. The approach you are discussing is very 'retro' to current / modern relational design practice. You need to really understand at least some of the basics, or you will build a major headache into you application. Please seek professional help or at least find the manual and go through the exercises. If you, for some reason, cannot get a manual or thrid party reference, at least go through the Nothwinds tutorial.


MichaelRed
redmsp@erols.com

There is never time to do it right but there is always time to do it over

 

[Brambojr]

ok, thank you all. I do own a few Access books and they do cover the normal forms so I will revisit them to make sure I really understand their content. If I understand the responses correctly, then I need a tbl for the equipment types (already have) and another with the, let's say, employee id and equipment type licensed where the employee may have multiple entries?? If so, how would I then make that into a very user friendly format to change and add to? This is really part hobby and I am doing this in an effort to learn and fill in any gaps in my "education" without relying to much on others. thanks again for the tips. Brambojr

 

[Brambojr]

Sorry, one last thing. I just reread my desriptions and think I have not done well explaining what is happening in the DB. One table does in fact only have Vehicle Type. The other table has Employee ID#, Date first trained, last date trained, and one column for each vehicle they may be licensed to use, one last column I have is a "Selected" column for the purpose of printing license plates but that doesn't really matter here. It seems to me that this is the best way to avoid repeating data, but again I am new to this side of DB (table) so am not ruling anything out as far as. . . well as far as me just missing a valid point.
The user would enter the person's name from a drop down (emp ID would be obtained) and they would then check off what the employee is licensed to drive. With the suggestions I have read it sounds like I would have even more repeat information than with this method. I am reading through the normalization steps, but . . . maybe I am missing something. What is it? Brambojr