Question 1 - Basically what I posted prior. A main table "usage" linked to a table "type equip" and also linked to a table "equip num" with relationships to keep integrity, cascade update correct?
I think you're starting to get the hang of things. This is a process, so try not to get discouraged. With your tblEquipNum, I recommend restructuring:
- tblEquipment
-
EquipID AutoNumber, PK
-
EquipNumber Identification of Equipment (as you have it now)
-
EquipType FK to tblEquipTypes
Then in tblEquipUsage, all you need is EquipID.
Question 2 - Being as I have tables to store the equipment type and equipment number is there a easy way to add new from the combobox. I do have some vba code but requires the table to be open.
I'm not sure what you mean (exactly). Are you asking if there is an easy way to add a piece of equipment so that you can use it on your form?
Yes - You could manually add it, but that's no fun. If a user can't find a piece of equipment from the drop down, have an "Add Equipment" button that brings up a small form which allows the user to add a piece of equipment. Then after they are done, it refreshed your Combo Box--this is s discussion for another thread.
Question 3 - Can the appearance of the datasheet view be modified? It opens enough space for 3 times the fields I actually have so basically much wider than needed.
1) I'd have to see what you are talking about because I'm not sure I understand.
2) As a general rule, I avoid datasheet view as much as possible. There can be several good uses, but I prefer to use form view so I can control what does into my DB.
Question 4 - Once I complete all my table sets such as Equip, Aggregate and so on how do I "join" the tables or join them in a query so that my report generates everything from the same date. I know you used some vba but I didn't really understand how it worked.
1) Question for another thread, but...
2) I get the impression that on each date "something" is occuring, such as, you view each date as a "production run" perhaps? If this is the case, then the "master table", if you will, would be something like tblProduction. Then, both the Aggregate and Equipment tables would have an FK to the ProductionID. Then you only have to record the date of the production run--all aggregate/equipment used for that ProductionID would be on that same date.
So............. .... to make a long story short, this shows the importance of planning out your DB very well before you start building it. This is not your fault, as you've probably never designed a DB from the ground up before. I think all of us who have been self-taught have learned these same principles over time. However, on the road of self-instruction, the main rule to always keep in mind is, "You'll never get it right the first time." As long as you understand that any "mistakes" you are making are out of inexperience, and you continue to learn from those previous attempts, all is good.
As I mentioned before, I think you are starting to move along the right road. This is a journey--not a destination. I continue to learn every day.
Hope this hepps!
174
