Are Lookup Fields in Tables Evil?

[Paul Howarth]

Because I'm a novice, I can't reconcile a Recommendation to always avoid using Lookup Fields in Tables, and the Requirement to use Lookup Fields for a Published Access database. (Sources pasted below.)


If Lookup Fields in Tables are a bad idea, then does that mean using Access to publish a database to the web is a bad idea too?


RECOMMENDATION
Thou shalt abhor the use of "Lookup Fields" which art the creation of the Evil One.
The Evils of Lookup Fields in Tables



REQUIREMENT
ACCWeb105016 Relationships that are not associated with a valid lookup field are incompatible with the Web.

What it means The relationship is not supported by a lookup field, and is therefore not compatible with a web database.

What to do Create a lookup field between the related tables. Use the Lookup Wizard to create the lookup.

http://office.microsoft.com/en-us/access-help/web-compatibility-check-relationship-and-lookup-errors-HA010379061.aspx?ver=14&app=msaccess.exe#BMaccweb105016

[NeoPa]

Paul Howarth:
Thou shalt abhor the use of "Lookup Fields" which art the creation of the Evil One.

I didn't see that particular text in the linked page Paul, but I get your drift (as you clearly got theirs).

I would say, in answer to your question, that you must do what you must do. Generally avoiding lookup fields is a good piece of advice as far as I'm concerned (for all the reasons listed in the article as well as not wanting to be too pally with said Evil One). Nevertheless, if they are required for a particular project to work, then use them in that situation.