User Profile
_brunoga
Copper Contributor
Joined Jun 28, 2021
User Widgets
Recent Discussions
Re: MS Access Many Junction Tables - Design Advice
George_Hepworth Gorge, I've seen your DB, your videos and I still couldn't understand how to do it. In that example of artists and songs it is a junction table with 2 tables involved and 2 keys (ArtistID and SongID). In this case I'm clear with it and the subform. In my case I will have 3 tables involved. Do you have an example with 3 tables?2.3KViews0likes1CommentRe: MS Access Many Junction Tables - Design Advice
George_Hepworth Prices will change every 3 to 6 months normally. If I stick to the previous relationship structure that I shared, is it possible to organize the form having the supplier selection in the header and then all the other details as a continuous form? Header carries all information from tbRequest and then user fill in ItemDescription (combobox) and fill prices and currency for that item (will probably add a checkbox like "use same currency for all items under the same supplier") Something like: I couldn't think how to transform my tbRequestDetails in this structure to the photo above, should I use a Query to organize?2.3KViews0likes3CommentsRe: MS Access Many Junction Tables - Design Advice
Hi George_Hepworth thanks for your quick reply, I'm in Asia, so our time zones are completely opposite haha When I meant save the price as per that date it is like: Request 1 on 01/01/21 Banana Price from supplier A is USD 1.00 Request 2 on 06/06/21 Banana Price from supplier A is USD 1.10 Technically, I don't need to have a field AsOfPriceDate, do I? I my mind I could use the RequestDate from tbRequest. This is my current template (done in excel), we have 1 row per item, first two columns the user will type the ItemType and Quantity and then is repeated 3 times the Price, Currency and Delivery. Basically I was trying to replace this template with access. So, an user will create a Purchase Request using 1, 2 or 3 quotation (depends of the total value). And then I need to store the information of: 1. RequestID 2. RequestDate 3. RequesterName 4. temCode 5. ItemQnt 6. ItemDeliveryDate These 6 fields are common to all suppliers. Then, once we include a supplier, user will need to fill the price for each item for that supplier and the currency. So, the price is liked to a date through the RequestID. Does it make sense?2.3KViews0likes5CommentsRe: MS Access Many Junction Tables - Design Advice
George_Hepworth Thanks for you reply. I've tried to create the relationships based in the concept above. Could you kindly check if is it correct? looking my tbRequestDetails, it seems quite repetitive. Am I doing a wrong way to key in the information?2.3KViews0likes7CommentsMS Access Many Junction Tables - Design Advice
Hi everyone, I hope everything is safe at your side. I'm trying to figure out in a model of relationship that could work for my case. Here is the situation: I have a tbPurchaseRequest that will have a tbPurchaseRequestDetails with the items' list (coming from tbMaterials). In one purchase request, I can have up to 3 Suppliers (stored in tbSupplier). The prices changes per supplier for each request, so, I need to capture the price for that specific request. Here are my doubts: 1. Where is the best table to capture the quantity requested and the price information? 2. What is the most logical way to organize this? Any advice?Solved2.7KViews0likes9Comments
Recent Blog Articles
No content to show