Database Reference
In-Depth Information
Repeat the steps above (adjust step 2 to choose the appropriate table) to create the following
TOs:
▪ Expenses_INVOICES
▪ Expenses_LINEITEMS
▪ Expenses_Invoices_LINEITEMS
▪ Expenses_JOBS
You now have five new table occurrences on your graph. Since the names are so long, you
might have to stretch your new TOs so you can read their names.
TIP
If you use the Duplicate button to copy an existing set of TOs, you get their existing names and rela-
tionships. Then you can move the new TOG and change its names and relationships as appropriate.
Or you can use a hybrid method of creating a new TO with the steps above, but copy/paste the pre-
fix part of the name from the first TO. With practice, you'll find your own favorite style.
Once you have your TOs in place, you need to hook them together properly. Here are the re-
lationships you need:
▪ From Expenses__EXPENSES to Expenses_JOBS, using the Job ID fields as keys. This
relationship lets you display the Job Name on the Assign Expenses layout.
▪ From Expenses__EXPENSES to Expenses_LINE ITEMS, using the Line Item ID field
as keys. The relationship will let you show a Line Item's detail on the layout.
▪ From Expenses_INVOICES to Expenses_Invoices_LINEITEMS, using the Invoice ID
fields as keys. This relationship will show an Invoice's Line Items on the new layout.
▪ From Expenses__EXPENSES to Expenses_INVOICES, using Global Invoice ID and In-
voice ID as keys.
After you create the Expenses__Expenses::Global Invoice ID to Expenses_Invoices::Invoice
ID relationship, notice that the global relationship shows a little bar on the Expenses side.
That's to remind you there's a global field on that side of the relationship. See the box below
to learn more about naming global fields.
Search WWH ::




Custom Search