The most important field in a table

A field that contains a unique identifier for each record in the table

A field that combines with a 'lock' type field

A binding agent. Used to join two tables together.

A field used in place of the key field. Used to more easily identify the record.

A field that references a URL. Used to link to another record.

To provide a temporary look at the type of data a field can store.

To capture a lookup field's value and not change if the lookup value changes in the future.

To create a copy of another field's value that can be used outside the app.

Using a lookup field.

Using a snapshot field.

Using a summary field.

Using a summary field.

Using an aggregate field.

Using a proxy field.

In the new key field's properties under the advanced settings.

On the left (parent) side of a relationship.

On the table's list of fields, using the 'set key' button.

The child records are updated to use the new key and the old key becomes a lookup field.

The child records become orphans and the old key is deleted.

Nothing, you cannot change a key field after relationships are built.

Yes, when you need both field types.

No, it is redundant to have both on the form.

Only if one is set to read-only.

When you don't have any good music to listen to.

When you need to select a parent record from a list.

When you are deleting multiple records and need to select them.

In the table's advanced settings.

In the record picker field settings.

In the default report settings.

In a table report, a chart, or dashboard.

As child records, as unrelated records, or as parent records.

As a link to the records, displayed as a report/chart, or in an editable report.

None, report links are only used on dashboards & homepages.

Up to 9, with 3 per row.

As many as you want.

Yes

No

The table is archived so that the relationship remains intact.

Both tables are deleted.

A "ghost relationship" remains connected to summary and lookup fields.

Their values are automatically converted to plain fields (text, numeric, etc).

Their values become null/empty.

They are automatically deleted along with the relationship.

It depends on the number of tables in the app.

It depends on the number of relationships in the app.

It depends on how the conditional dropdowns are constructed.

Using the right (child side) of a relationship OR using the 'same row' option in the form's elements.

Using a multiple-choice field with a related reference field OR using two related reference fields.

Using a proxy field with a multiple-choice field OR using a proxy with a multi-select field.

By using a report as the record picker with the filter built into the report.

By deleting records that you don't want to appear in the dropdown.

By adding a filter to the table's default report settings.

True

False

True

False