Recent content by jjatwork

I'm starting to see that this is actually a core point of relational databases. I did not realize it for a while, I must admit.

I don't really know the netiquette around adressing multiple/specific people, but those @'s don't feel right. Dave, the memo notes field is a good solution, but I'm afraid have oversimplified things in my attempt to be brief. I actually need two strings, one for the repairs done under warrenty...

Sorry about the delay. Been off for the holiday. @ Doc. Thanks again for the explanation. I've been doing some reading on architecture fundamentals, but there's a lot to take in all at once. @ Dave. Yes, in theory a flag in the table would do the trick. The problem is, that I've been asked to...

@ Doc Thanks for the detailed walkthrough. I've already separated Entities like Dept. and Team, which has lots of additional info like address, phonenumber etc. into their own tables, but I was unsure how to deal with things like colour and size, which will only have a few fields in their...

Thank you for the confirmation and the in-depth explanation. It certainly helps me understand the issue! I've done some reading and now better understand what entities and lookup values are. Just a quick question, though. In this case, the colour would still be an attribute of the entity (the...

It certainly helps, thank you. So, if I understand correct, in case of a n:1 relations, I would keep the field in the 'primary' table to hold a FK, whereas in the case of n:n I would make a junction table. Or am I trying to oversimplify it? I'm not sure what a lookup value is, but the reason...

I've done a lot of reading on normalization, but I'm having a hard time grasping some of the concepts. Especially how to use foreign keys and junction tables. Let's say I have a DB where I keep track of bicycles. I have a table, 'tblBikeInfo' with a lot of fields containing info about each...

Thank you. That was exactly my thinking, I just wanted to make sure. JJ

Since the thread hasn't been closed yet, I'll provide a small update. I've been studying up on normalization and trying to clean up the DB. Lots of trial and error had resulted in some redundant code and tables/queries. Additionally, I've nearly finished removing any sensitive data from the DB...

First off: I think the answer to the OP is to redo the mess. If any mod wants to mark the thread solved and/or closed, feel free. Thanks for the advice. I always find it inspiring to hear stories from those who have experienced the evolution of programming first hand. I'm already a bit lost...

Hello Mark. Tyvm for your time. This is by far my preferred choice! But I only have a vague idea about how the buttons should be programmed to function with such a table. Which is why I focused on the dirty fix. Hi Doc. The names are just placeholders. Real labels are 'Brakepads...

I think my question might have been very poorly worded and not thought through. My problem was actually in printing the invoice, but even if I could apply the fix I had in mind, it would not be a good solution, as it doesn't allow me to extract any other information than the label and the value...

Hi Dave. Thank you for your reply. Going by what you wrote, I'm even more certain that I'm doing this the wrong way. To add some info, this DB is meant for a fleet of bikes and the invoice form is used for billing some of the repairs. As it is, all parts are listed on the form and small '+/-'...

Tyvm Gizmo. I'll check it out right away. The Northwind template uses a dropdown menu to add items to the invoice, which my client doesn't like. No doubt I'll pick up a few useful things, though, so I appreciate the link. JJ EDIT: And thank you for the extended comment too.

Thank you both for the warm welcome. JJ