Search results

Okay, well as long as I'm not crazy :) I redid the relationships but I don't quite understand the logic of it. What makes this set-up better than the simpler version (three FK's in tblJewelryInventory only)? Thanks again for your help!

Okay, so I've set this up according to your post and this is what I've come up with. I don't understand the point in linking tblCollection and tblDesignName together and tblDesignName if we are not using the composite key from tblCollectionLink. Also, why create unique combinations of...

Just when I thought I had this all figured out! I knew memos were not preferred but didn't know I should separate them out. I'll make sure to do that, thanks! I really appreciate your time and help! I'll report back, but may not be until Monday.

I'm going to set it up both ways. I don't particularly care the way in which its set up, as long as it won't cause me trouble and its straightforward to manipulate. The collection history field is a memo that has a paragraph or two that describes the background of how the design was imagined...

I understand what you're saying, but it just looks weird to me. I'm certainly not disputing what you say! I attached a screenshot of how I have it set up now.

With this set up, I'm stating that Tears | Ring can be apart of multiple Collections, right? Why wouldn't I put tblCollection, tblJewelryType and tblDesignName all together with a link table?

So there are many collections (collection 1, collection 2, etc). Each of these collections can have many Designs (design 1, design 2, etc). Each of these designs will have a type of jewelry (ring, necklace, etc). What's in there is just junk data to help me figure things out. An example of...

Okay, here's the spreadsheet. I also uploaded the db in case you needed to see it for any reason.

Yes, they actually have associated records in each table. It's the same as country > state > city. I attached an example of how the data is related. The left column is what I'm storing in tbljeweleryinventory and the right column is what I'm storing in tblInventoryLink.

Oh, I see what you're saying now. Yes, I need to fix the naming so it's consistent. Yes, I set it up this way so I could cascade them. Is this not the correct way to structure the tables for this purpose? I thought that since they are cascaded, then JewelryTypePK would end up being the...

No, I appreciate all the input. Want to build it right the first time! The reason for the FK in those tables is because I thought I needed that to ensure they would cascade correctly. Do I need to keep my current relationships and also create the two new ones you recommended?

Okay, I'll look into setting up a DCount for this. Do I need to delete the relationships between tblCollection and tblDesignName? I have a set of 3 nested forms set up that I'm going to use to enter the data into to ensure that they still cascade properly. Will that be a problem?

I have three cascading combo boxes. How can I program a button to record the PK's from these combos into a table, but only if those values don't already exist. The 3 combos are circled in red and I want to record those values into tblJewelryInventory (circled in dark blue).

Should I be storing the PK's for all three combo boxes somewhere, or just the last combo? I'm storing cbo1 PK in the table that supplies cbo2. cbo2 PK in the table that supplies cbo3 and the PK for cbo3 in a "main" table that has a few other data points. Is setting a filter better or worse...

My preferred action is that the three combos are cascading and after I select the three boxes, the subform is filtered to match the criteria.

I think part of the problem is that the data in these combo boxes won't change very often and I'll be using the data in them over and over. Can I set up bound combo boxes so when I select the data in them, it's recorded? For example, if I have Collection 1, Design 1, Jewelry 1; this can...

I have to admit that I've been working on this all morning. I have tried changing the tables so they support cascading combo boxes but I keep getting errors when trying to select data. I'm not sure that I can adequately explain what I'm trying to do in words so I'm going to upload the db to...

I've attached a screen shot of the relationships. In the red circled tables, I'd like to use the PK from tblJewelryType, tblCollection, tblDesignName to look up the PK from tblJewelryInventory from three combo boxes on the form. Each combination of those three PK's may have multiple...

Nevermind, I'm just bad at this I suppose. I was including the query that I was pulling the data from and that was causing multiple records. I forgot I don't need to incorporate that query and that I can just call the concat function without it.

Thanks, that works a charm. So it was as simple as removing the DISTINCT from the code and/or the query so there was only one DISTINCT? I saw that you commented the line out of the code. Wow, I feel like a dummy. Kind of similarly, will this code always limit the result of the concatenation...