Subject | Views or Lookups |
---|---|
Author | zifnabbe@users.sourceforge.net |
Post date | 2001-12-02T15:13:57Z |
Hi,
Is it better to make views (which join a view tables), or make use of
DBLookup fields?
For instance, I've a number of a region and I've the region name.
A person links to a region by a region ID.
Now, if I show the persons information, I've to show the ID of the
region, but also the region name (which is stored in another table).
I could make a query or a view which makes one table with all the
information, but I could also use a DBLookUp field which looks up the
regionname per regionID.
What is the best approach?
Thanks,
Tom.
Is it better to make views (which join a view tables), or make use of
DBLookup fields?
For instance, I've a number of a region and I've the region name.
A person links to a region by a region ID.
Now, if I show the persons information, I've to show the ID of the
region, but also the region name (which is stored in another table).
I could make a query or a view which makes one table with all the
information, but I could also use a DBLookUp field which looks up the
regionname per regionID.
What is the best approach?
Thanks,
Tom.