I have to start a new project. One of the forms needs to be like a checklist. There will be 39 items that will have 4 options each. The 4 options will only be checkboxes. I have to store this information. The only way that "I" know how to go about this is to actually start a table with 156 fields (39 x 4) or 39 tables with 4 fields each, either way sounds wrong. Is there a better way to set up my table/form, without having this tremendous amount of data. I thought of just creating a new table for each entry, but in a couple of years there would be a couple thousand tables, and that definately seems wrong. The database will be set up to store the evaluation of parts that come in an assembly. The assemblies each have 39 parts. The 4 options are REPLACE, REWORK, REUSE, and IN STOCK FOR USE. Any help would be appreciated.
What is the best way to start my new project.
Collapse
X
-
Tags: None
-
These things are usually very time consuming! You might want to download and look at Duane Hookums’ Survey Database
At Your Survey
Originally posted by Duane HookomAt Your Survey is provided for educational purposes only. Steal ideas and methods but not the whole of the application. This runs in Access 2000.
Linq ;0)> -
-
-
The bulk of it will be the different parts of a valve assembly
stem
packing gland
bonnet
and 36 other parts
each one will have a disposition that is one of these 3 (the fourth option that i talked about earlier really doesn't apply)
replace
rework
reuse
I had thought that i would make it look like the form(paper) that is currently used. I realized that this would be silly to make 3 checkboxes for each item, and that it would be better to just put a combo box on each item, to choose 1 of the 3 options. That way each record is storing 1 datum for each item, instead of storing 2 false fields and 1 true field, for each item.
I made a table with each item listed
I made another table with the 3 options listed, so that i can just get the info from there and have the combo box list the items from the table.
If this is the wrong approach so far please let me know. I will work furiously until someone suggests that i change it.Comment
-
I would add a disposition field to the parts table.
Probably I would chose on the form for a frame with three radio buttons that's used to show/select the actual disposition.
You'll have to check or you need the date of setting the disposition and / or a history is needed. Sometimes even the user setting the value is needed to record, thus making it possible to ask a colleague why he changed the setting...
Nic;o)Comment
Comment