lookup wizard fields table

[mikevds]

I have a products database
I have a table name of products, catagory, subcatagory number
Also a another related table that has catagory name associated with auto number same with subcatagory number

With the Products table I entered in everything like number 1, associated with the auto numbr with the catagory name with that product
I did a lookup wizard in the table so it displays that catagory with the name instead of the number.
IS this the correct thing or should I wait till I design the form?

 

[pbaldy]

I wouldn't do it:

http://www.mvps.org/access/lookupfields.htm

 

[wiklendt]

I wouldn't do it:

http://www.mvps.org/access/lookupfields.htm

i have a gripe with point #3 in that link, which states:

3. Another relationship is created which then creates another set of indexes when a Lookup field is created, thus bloating the database unnecessarily.

a relationship is made in a RELATIONAL DATABASE??????! Gasp!! EEEEVIL!!!!

why is this BAD? isn't this the whole POINT of a database? how else does the database know to link up this field in this table, with this data in that table??

(edit: and wouldn't "compact and repair" de-bloat this kind of thing?)

as for #7 and #8

7. The database cannot be properly upsized to, or queried by, another engine (without removing all the lookup fields) because no other engines use or understand them.

8. If security is implemented, permissions to tables is usually denied, and RWOP queries are used for data access. There will often be errors that there are no permissions on a specific table that isn't even being used in a query (because the lookup field is). If the queries are nested or complex, it can take some time to track down the lookup that's causing the error (that is, if it occurs to you).

hm. didn't know that. that's a good point and could be an issue for a lot of people (lickily not for me yet: my DB's haven't been so far-out to need such high-end implementation.)

as for the other points mentioned, if you're good with your databases and know of these facts, then they won't bother you or your database. e.g. i know that i can't search for a company name when my table has a companyID/companyName lookup - i know that to search for this name i need to throw the company table into the query also, and query the company name from the company table, and ensure i have my join properties correct...

 

[mikevds]

Thanks,
I could't remember because the last database I set up was last year.

Anyway, I see what you mean that for the products table for the catagory I will just have number 3 for example if the autonumber of the caragory table let's say the autonumber number 3 is chocolate candy,
then I will set up the lookup wizard through my form.

I tied looking at a previous database music, but just couldn't remmber the tables for cdname was a autonumber and author number was just a number not a lookup wizard.

Thanks alot again.


Regards,