Lookup

[Shelley]

When using a List Box in the Table Design Mode, what does each item in the Lookup Properties refer to and what it will cause to happen when changed?

For example:

My Table has the following data:

Bends Setup Time Needed
Per Bend

Cover Bend 10
Accessory Bend 5

I would like to have each Type of Bend be able to automatically fill in the mandatory Setup Time Needed Per Bend. I am thinking that if I do this in the Table; then it should also carry over into my Queries and Reports too according to what I've heard and read.

I don't quite know how to tell Access to do this and I don't know what each of the Properties in the Lookup tab at the bottom refers to and no one ever really discusses them in the tutorials.

I also want to make sure that I have these Properties for Lookup set correctly for any of my other List Boxes too.

[RuralGuy]

Here's something you need to read: http://access.mvps.org/access/lookupfields.htm

[Shelley]

According to all of the online videos and instructors, so long as I'm not using a primary key in my Lookup Table, then this is supposedly the most accurate way of doing this.

If you don't agree with this method, then would you please explain to me what the appropriate way of doing it is?

Many thanks for your assistance regarding this matter.

[RuralGuy]

Does your first post indicate there are 15 types of bends?

[Shelley]

No, there are probably only 5 or 10 different types of bends. The 10 or 5 are referring to how many minutes it takes the operator to perform each one.

[RuralGuy]

The Lookup Table should probably be:
BendID : AutoNumber - Primary Key to table
BendDesc : Text
SetupTime : Currency - So you can use decimals but not floating point number

[RuralGuy]

You can then use the power of the Join to include the setup time in queries and reports. No Lookup Fields involved. I am curious to know what videos and on-lone instruction you have been reviewing.

[Shelley]

But wouldn't that interfere with queries and reports that would be run against it?
Especially since it is not actually a monetary value.
I will need to have a few different bends for the supervisors to pick from when entering their data too.

[RuralGuy]

Nope, if you are referring to the Currency datatype. Displaying the "$" is just a formatting option for display and not necessary although it is the default for that datatype. A Currency field is just a special type of integer field that can take a decimal.

[Shelley]

Richard Rost Videos https://www.youtube.com/watch?v=ySyMn3H4rvg

Trainer Lori https://www.youtube.com/watch?v=BPDs_55USOY

Just to name a few

[Shelley]

The Table Bends will later be used to create Queries, Reports and Forms too. The Forms will be using expressions with this data to provide other information too.

[RuralGuy]

Not a problem. With Joins you can treat more than one table as if it were one. It's magic!

[RuralGuy]

If I haven't mentioned it yet, Lookups (Combo Boxes) on forms are just fine! It is only when they are at the table level there are issues.