Remember the value for later use

[trythis]

Hi,

I need some clarification about look up fields.

is it better to do them at table level or Form level?

If you do them at form level what is the advantage of remember the value for later use vs. store that value in this field

Thanks,
Tina

 

[boblarson]

Hi,

I need some clarification about look up fields.

is it better to do them at table level or Form level?

If you do them at form level what is the advantage of remember the value for later use vs. store that value in this field

Thanks,
Tina

Form level most assuredly. See here for why.

As for later use and store this value - it all depends on what you are using it for. If you are using, say a combo box, and you want to use it to search a form, then save for later use is the selection (it just means use the value) and the store in field is for if you want to make a selection to add, say the ID of an employee to a certain table where you select the name but the ID is populated.

Does that help?

 

[Scooterbug]

Lookups at table level are evil. They cause nothing but complications.

When you elect to store the value, the value is saved in the field the control is bound to with the record. When you choose to remember, it remembers the value as long as you are on that record.

 

[boblarson]

it remembers the value as long as you are on that record.

Actually, if it isn't a bound control then it will remember as long as that selection is there or until the form is closed.

 

[trythis]

Ok, a Form level look up field is best. I am glad to know because I was screaming trying to get table level look ups to work and I thought I was crazy.

I can just store the value in the employeeid field because I have the relationship to show the name in the report or form later.

Right?

I have a table that I emport and it has
sheduleid
employeeid
employeename
departmentid
positionid
starttime
endtime

I have these tables and primary keys
employeeid
departmentid
positionid
and these have the descriptions for the specific ids

I could just take out the employeename from the first table since I have the table that tells me what the name is from the emplyee id. that is redundant to have the name in both. Right?

any clarification would be great.

Thanks,
Tina

 

[boblarson]

So when I use form level look ups and for example I have
employeeid
employeename

I can just store the value in the employeeid field because in the relationship to show the name in the report or form later. Right?

Correct

I could just take out the employeename from the first table since I have the table that tells me what the name is from the emplyee id.

Correct