Search results

Looks great! Yes, this can get incredibly complex especially when you start needed more functions, which means more tables, forms, subforms, queries, reports. Never mind code if that happens. Now that you are on solid ground with your table structure you should be good to go. Good luck with...

Equally important for grouping is putting the equipment into one field rather than 4+ separate fields. This way your reports will be easy to make since you can easily group by employee or equipment type and get meaningful results.

No problem. BTW, you might as well add a field called CheckInDate to your Checkout table to keep track of when equipment comes in. By structuring the tables properly and normalizing them, you will have much more control over the data later on even if it seems counter-intuitive to do it...

you need to separate everything into distinct functions and break everything down into the most basic components. You really should read up on the subject or normalization and relational database design. There is only so much anyone on here can help if you do not understand the fundamental...

The way you are trying to do it is not normalized. All of these are types of equipment and should go under one field. So the field is EquipmentType or something similar and the records are: Phone Radio Spotter etc. Each of these will be its own "record" or row in a table (not a column). If...

Ok, I now realize I made a mistake: you don't need both tblEmployeesEquipment and tblEquipmentCheckout because they are basically the same (except the latter has a checkoutdate). So, you can just add the CheckoutDate field to tblEmployeesEquipment and get rid of tblEquipmentCheckout. Does...

I should have been even more clear: in tblEquipment your fieldname should be EquipmentName or something like that. If you have several models under the same type of equipment (so 10 phones, for example) you will need to think through some more

The relationship between tblEmployees and tblEmployeesEquipment looks good. tblEquipment needs some work. Basically you should ONLY store equipment types in there. You need yet another junction table for checkouts. tblEquipmentCheckout EquipmentCheckoutID (FK) EquipmentID (FK to...

No it would still be putting the data into the junction table. EquipmentID would be a lookup to tblEquipment and the ID# would be saved in the junction table. Yes subforms do the same thing: it will enter the data into your junction table just like the main form will enter it into your main...

So, you should not have three separate equipment fields. Phone, Radio and Gas Detector should also be in one equipment field.

For one, you can make a subform look as if it is not a subform if you are crafty. But yes, it is a separate form to maintain. You may be able to get away with making the recordsource on the main form a query based on tblEmployees and tblEmployeesEquipment but it is not recommended. On another...

In most cases, you would use a subform if you are entering information from different tables into a form. Generally the main form would be based on your main table and your subform would be based on a junction table. This is the typical scenario. So, you would have an employees form based on...

Generally this is a fairly simple thing to achieve. However, in this case it is hard to say how to do it without more details. Where is the list coming from? How is it getting the data? Is the listbox based on a query and, if so, is the ID field being stored in a query on which the listbox...

Yes, that is likely the reason. I still have 2007. What is the recordsource you are using for your main form? Does the form include a subform?

Also, unless the lookups are in value lists (and are not FKs to other tables), you should remove them from your tables and change the data type to number.

20 forms sounds like a lot but can some be combined with subforms? Are these 20 distinct tables with no relationships (if so, why? that shouldn't be)? I am sure there is some way to design this properly and not end up with dozens of forms.

You should create a simple form and be done with it.

I cannot open your database.

I will take a look but first things first: you should not name your junction table tblJunction. Name it something like tblEmployeesEquipment The reason being that if your database grows and you have more tables and more junction tables, this name will not be very useful. You should make it...

This is an excel table :confused: I thought you were posting your database... Make sure your field names do not have spaces in them. I noticed there were spaces in the Excel sheet. Family should be its own table: put all the family names in there and put FamilyID as the FK in your species...