bound column issues

[Guest]

I've got a table that has a listing of assembly lines and then the production
times associated making one unit on each line. I've got a lookup cell in
another table that has the process time as the bound column. Two different
assembly lines have the same process time. When I try and pick the second of
those two lines, it won't allow me and chooses the first one for me. How can
I get it to allow me to pick a different line even if that line has the same
process time? I have it bound to process time because I'm using the times in
a calculation later on. Thanks in advance.

 

[Al Camp]

Mark,
Pretty hard to say for sure, but...
Showing us the 2 data entries with fieldnames and values would help, as well as your
"lookup" expression.
It sounds like you haven't differentiated the two production lines, or your lookup
isn't filtering properly for the correct record.

What differentiates the data from ProdLine1 from ProdLine2?

 

[Guest]

I'll try my best...

I have a table called Glass Lines. In this table there are 4 columns:
LineID, an AutoNumber primary key; Line, a list of assembly lines; Time, a
list of the process times; and Date, the date the process times were entered.
This table serves as the source of the lookup. The entries that are messing
up in this table are...

LineID: 5, Line: Glass Line 1, Time: 10, Date 8/2/2006
LineID: 7, Line: Glass Line 3, Time: 10, Date 8/2/2006

I also have a table called GlassMainMenu. This table keeps track of all
sources of downtime and other values needed for my calculations I make in my
queries later on. The time column in this table has the following lookup
properties...

Row Source: SELECT [Glass Lines].LineID, [Glass Lines].Line, [Glass
Lines].Time, [Glass Lines].Date FROM [Glass Lines];

Bound Column: 3

Does that help?

 

[Al Camp]

Mark,
First, don't use fieldnames of [Date] and [Time]. These are reserved words in Access
and will cause problems.
Try something like OutageDate and OutageTime.

You used the term "lookup", but I gather it's a combobox (or list box... same
solution).

Try this Column Setup...
Column Order would be LineID, OutageDate, OutageTime, Line
Try this Combo Setup...
Columns = 4
ColumnWidths = 0"; 1"; 1"; 1"
BoundColumn = 1

This will select a LineID... which is discrete enough to find the proper line... in the
bound field (works bound or unbound), but will display the OutageDate in the combo.

Binding the combo to column 3 (OutageDate) isn't discrete enough to find the specific
record you want when there are duplicates. It finds the first record with that date value
in the query. You need to bind to a discrete value such as LineID to find ONLY that
record.

If you must keep the Column Order LineID, Line, OutageTime, OutageDate... use that
order with the same combo setup as above, but place a calculated field next to the combo
with a ControlSource of...
= cboYourComboName.Column(3)
That will always display the OutageDate whenever a LineID is selected. (The combo will
display the Line... the first visible column in the combo)

--
hth
Al Camp
Candia Computer Consulting - Candia NH
http://home.comcast.net/~cccsolutions

I'll try my best...

I have a table called Glass Lines. In this table there are 4 columns:
LineID, an AutoNumber primary key; Line, a list of assembly lines; Time, a
list of the process times; and Date, the date the process times were entered.
This table serves as the source of the lookup. The entries that are messing
up in this table are...

LineID: 5, Line: Glass Line 1, Time: 10, Date 8/2/2006
LineID: 7, Line: Glass Line 3, Time: 10, Date 8/2/2006

I also have a table called GlassMainMenu. This table keeps track of all
sources of downtime and other values needed for my calculations I make in my
queries later on. The time column in this table has the following lookup
properties...

Row Source: SELECT [Glass Lines].LineID, [Glass Lines].Line, [Glass
Lines].Time, [Glass Lines].Date FROM [Glass Lines];

Bound Column: 3

Does that help?

Mark,
Pretty hard to say for sure, but...
Showing us the 2 data entries with fieldnames and values would help, as well as your
"lookup" expression.
It sounds like you haven't differentiated the two production lines, or your lookup
isn't filtering properly for the correct record.

What differentiates the data from ProdLine1 from ProdLine2?

--
hth
Al Camp
Candia Computer Consulting - Candia NH
http://home.comcast.net/~cccsolutions