If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Display Modes |
#12
|
|||
|
|||
Best way to design tables for cascading on my form
You are correct about the junction table. Note that what Steve suggested (I
described something similar) is only a way of building a list of parts that are associated with vehicle types (although I don't see that you need hidden text boxes). My previous posting described how to use the resulting data to limit the listing of available parts on the Claims form. To sum up, you need a list of parts associated with a Vehicle Type THEN you need to use that list to provide the Row Source for a combo box on the Claim Details subform on the Claims form. It should be possible to add an extra field to tblPart to indicate whether the part is on all vehicles. Your combo box list could incorporate the custom list for the vehicle type, plus the default parts that are associated with all vehicles. Pamela wrote: Thanks for that suggestion, Steve. I followed your instructions and created the 3rd table, which as I understand is a junction table between VehType & Parts. I don't see, however, how/where the VehTypes get matched with their respective parts. As I understand, the query you had me build is not updateable so how do I match them?? Thanks so much for your help with this! Pamela First you need tables like the following: TblVehType [quoted text clipped - 59 lines] . -- Message posted via http://www.accessmonster.com |
#13
|
|||
|
|||
Best way to design tables for cascading on my form
Thanks so much, Bruce. I'm sorry that this appears to be a very late reply,
but for whatever reason, my system (or perhaps it was the website) wasn't correctly displaying the responses here for a few days. This VehType/Part situation is really just what someone else has called ancillary data - going to be used only one time per file which is why the idea of the Parts being displayed in a Multi-Select list box which doesn't save the users choices after leaving that record really isn't a problem. I want to get this portion up and running but then I also want to grow this db to emcompass much more of the work we have to do so I'm always wanting to make sure I'm not hindering myself for that future growth. With that in mind, you suggested to make a tblClaim (which I have) but in it, you listed the vehicle Make & Model. All of my designs have had a separate tblVehicle because it seemed that having the Vehicle info in w/ the Claim info broke normalization rules. Now if that was just a fast example to try to illustrate to me how to connect all of this VehType/Parts to the actual claim, I can understand that but if there is another reason you would put those together, I'd be very interested in the thought behind it. Thanks so much! Pamela "BruceM via AccessMonster.com" wrote: You are correct about the junction table. Note that what Steve suggested (I described something similar) is only a way of building a list of parts that are associated with vehicle types (although I don't see that you need hidden text boxes). My previous posting described how to use the resulting data to limit the listing of available parts on the Claims form. To sum up, you need a list of parts associated with a Vehicle Type THEN you need to use that list to provide the Row Source for a combo box on the Claim Details subform on the Claims form. It should be possible to add an extra field to tblPart to indicate whether the part is on all vehicles. Your combo box list could incorporate the custom list for the vehicle type, plus the default parts that are associated with all vehicles. Pamela wrote: Thanks for that suggestion, Steve. I followed your instructions and created the 3rd table, which as I understand is a junction table between VehType & Parts. I don't see, however, how/where the VehTypes get matched with their respective parts. As I understand, the query you had me build is not updateable so how do I match them?? Thanks so much for your help with this! Pamela First you need tables like the following: TblVehType [quoted text clipped - 59 lines] . -- Message posted via http://www.accessmonster.com . |
|
Thread Tools | |
Display Modes | |
|
|