Subtitles of the Movie

Well, one of my favorites is this ability to change the color or something. We can select one of these and change it to any color we want, and this can help us by organizing by color. So we might actually come over here and say let's click on Customers and choose select tables with same source table, and you can see how all of the customers are now selected and I could change them to a particular color, like let's say red, or I could come in here and say let's choose Lines here, select related tables one way. You can see how it selects this one and this one, only one relationship away. If you give an example of zips, you'll see it'll do something a little bit different, so try to familiarize yourself with all of the features here. What I'm going to do is I'm going to go through and label each color here. I'll make that green, make Lines blue. Let's try that. Make Products, we'll make that one purple, try that one right there, and let's see, Invoices, well, we should have selected all. There's an Invoices Customers here, so we'll choose the same green. There's Lines, we need to choose the same blue. There we go. And then we'll just leave Zips gray for right now, this it's not really a major player here. So that might help you out, but you might want to select all of your structural relationships and change them all to a specific color so when you come in, you can quickly see that and then all the supporting relationships will be different colors. There's so many ways you can use these colors. Then, of course, you have your default tool, the arrow tool which lets you click on things, your text tool, and when you get it, you need to draw yourself a little post-it note, Important Information Here. When you click, you can change color, font size, all that kind of good stuff, and you can resize it by getting on the edges here. You can toggle it, but a really cool thing you can do is you can actually draw it behind all these things and you can say this is an organizational structure here. I'm going to organize all of these together and say these are this particular type of table occurrence. It's up to you how you do this, but this is a common thing. Just put this behind, so you can really group these together, so I'm going to get rid of that note there, though. I'm not particularly fond of them that much. I feel if you have it organized really well and colored really well, you don't need notes, but it's up to you. Then you can, of course, make your graph smaller or make it bigger. In fact, while you're down here, you can show your pages, case. If we make it even smaller, it might help. You can see where the page breaks are, so when you print, you'll see if it comes out all on a page. You, of course, have your page setup here and then you can come back up or you can click on this button right here and you see it takes it to 95 percent, not quite 100 percent, let me turn that off, because it's trying to fit the whole graph into one page, but you certainly can come in here and type 100 and once you click out of there, it'll switch it to that, so it's up to you how you work with this, just make sure you know each one of these features, but I'm going to also show you one other little thing. I'm going to add a couple of table occurrences. We'll add one for Invoices here and we'll mov these two down here, and we can connect these, so I want to introduce you to a concept. I can connect these two and not connect them to the rest of the relationship graph and in complicated solutions, this is very often the case. What you do is you try to arrange these groupings of table occurrences so they work by layout. So you might, in this situation, could have had Customers over here and you could have had Invoices and Lines and you could have had all these different table occurrence groups based on what layout it is, so we have, basically we worked with customers and invoices, so we could have had two table occurrence groups and what you end up doing here is you get more table occurrences this way because obviously in this case we'll have to add one for Lines if we want to see that information. It goes over here, KP Invoice to KF Invoice ID, because if we have a layout, let's say, based on Customers, that can look at Invoices and we want to look at Lines, we can't use this Lines up here to display the information. We have to duplicate that table occurrence for this grouping. So you have to consider is my solution complicated enough to need to do that? Right now, it's certainly not. There's not very much going on here. But if it is, if you've got, let's say 50 or 100 table occurrences, well, you may need to do this grouping and you really should decide that at the beginning, and again, you decide it by layout, so this might be all of the table occurrences for Invoices Layout and this might be all of the ones for Customers, so base it on Layout, consider this as a possibility. I'm just planting a seed here to give you an idea. You don't have to do it at first. Probably your first couple of solutions will have just a big, giant spider relationship graph, but I want to plant a seed of what you can do with table occurrence groups, so we'll delete that, remove it. Hopefully you have something like this. Play around with it, make it look nice and neat, and you'll be ready to go.