"Enter Parameter Value" when trying to open a table with look up field..?

[synses]

When I try to open a table I created that has a few look up fields in it, I get a message pop-up that says "Enter Parameter Value"


What have I done wrong and how can I correct it?
Thanks for any help you can offer,
Synthia

[Micron]

Some would say the first thing you did wrong was create lookup fields in a table.
Perhaps you no longer have that field in the table, but it remains in an Order By or Filter property?
EDIT: or if the values are coming from another table, is that table and the field correctly referenced/named, and is the table linked and the link is still valid/working?

[synses]

Thanks for the ideas, I will double check the links and tables/fields that are linked.

What would you suggest doing instead of using look up fields to auto populate/connect one field in one table to another table?

I am new (ha! old new...) and want to learn to do it correctly.
Thanks for any suggestions you have to offer,
Synthia

[rpeare]

if you are using the data structure I gave you in your other post, you don't need to create links to the foreign tables if you are looking at data entry. You only need the source table as a record source. When you go to a particular record if your data entry field is a combo box with a source of tblRole where the first column is the primary key and the second column is the role description, then all you have to do is suppress the first column (width of 0 (zero)) and you will correctly display the role description.

[synses]

Thanks, I assumed it was a look up function, and used the look up wizard, when connecting .say the people table to the role table, etc., I will study what you said here with the other message better. (tomorrow, start over, again, and STILL very grateful for the help!)

[Micron]

Not familiar with the other post so not sure if this is helpful. If you need to control what a person can enter into a field, one way is through code, but a (perhaps) better way is to have lookup tables. For example, you create a table tblDepts and list every department in the scope of the database and perhaps a field to flag it as current or not (could be ObsoleteDate). This way if you add or rename a department, not only do you simply add a record to that table (or edit it), whereupon it automatically becomes available to cmbDept, but it doesn't require you to alter table design. As for populating tables using such controls, you should use forms. Here's why NOT to use lookup fields:

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