Database Reference
In-Depth Information
TIP
Remember, if you like things lined up nice and neat, you have Arrange tools that let you resize and
align a selected group of TOs together ( Arrange the Graph ).
Building the Assign Expenses Layout
Now that you've finished the new table occurrence group and hooked up its relationships,
you're ready to create the Assign Expenses layout. Since this new layout has a lot of objects,
you'll have to repeat some processes a few times. Figure 14-16 shows what you're trying to
accomplish.
POWER USERS' CLINIC: ONE (GLOBAL) FIELD TO RULE THEM ALL
You know that fields set to use global storage have the same value across every record in the table
that holds them. Since these fields are so different from other fields, many database designers give
them special names so that the fields stand out in a list. That way, they're less likely to get used in-
appropriately—say in a context where they don't have much meaning—or plopped down on a lay-
out where someone can edit the values when they should stay static.
You can just preface the names of all your global fields with the word “global,” like you did in the
steps above. But in the real world, people commonly just use a lowercase “g” as a prefix. With this
scheme, you can name your global field “gInvoice ID” and save a few keystrokes. Plus, you look
like a guru.
Some developers also use the lowercase “g” in the names of their TOs, to indicate that the relation-
ship uses a global field as a key. It can be a handy extra reminder that the relationship doesn't work
bidirectionally, as relationships that are based on normal fields do.
Search WWH ::




Custom Search