Lookup fields in tables yes or no

When I first started designing tables i used many lookups resulting in many
relationships between tables. I started noticing some performance problems
so I went to no lookup fileds in the tables but put them in the forms. I
also did the same with formats. This does cause a little more work in
queries, forms and reports but it seems to be working well. Does this new
approach make sense?

"Eric Blitzer" wrote in message
...
When I first started designing tables i used many lookups resulting in
many
relationships between tables. I started noticing some performance
problems
so I went to no lookup fileds in the tables but put them in the forms. I
also did the same with formats. This does cause a little more work in
queries, forms and reports but it seems to be working well. Does this new
approach make sense?

Yes, see the evils of lookup fields at:
http://www.mvps.org/access/lookupfields.htm

"Eric Blitzer" wrote:

When I first started designing tables i used many lookups resulting in many
relationships between tables. I started noticing some performance problems
so I went to no lookup fileds in the tables but put them in the forms. I
also did the same with formats. This does cause a little more work in
queries, forms and reports but it seems to be working well. Does this new
approach make sense?

Lookup fields are never *necessary* - and they do indeed have disadvantages,
as noted elsethread.

However, you should use SOME tool to create enforced relationships between
your tables. The lookup wizard does this (badly, creating duplicate
relationships if they already exist), or you can use the Relationships
window. Just creating "lookups" on a Form does NOT ensure that your data is
properly related.

--
John W. Vinson[MVP]