Linking columns

[edunker]

Is it possible to update the text in tblSIGNS column Open_Work_Order to say yes if tblHISTORY Column Urgency is High, Medium, or Low for the same Sign id that is in both tables(tblhistory column name is SIGN_ID and tblSigns column name is SIGNID) and tblSIGNS column Open_Work_Order to say no when tblHISTORY Column Urgency says Completed. In my form that is bound to tblSIGNS I have a text box that is bound to Open_Work_Order.

[zmbd]

Ok,
You have ran your question into a really jumbled mess...

+ Nomenclature, I understand that the tables look like worksheets; however, in Access:
++ data tables have records - not rows
++ Records have fields - not columns.
Using the proper terms helps to keep your question clear.

Next:
Table named: [tblSigns]
Field named: [Open_Work_Order]
Field named: [SIGNID]

Table named: [tblHISTORY]
Field named: [Urgency]
Field named: [SIGN_ID]

You want:
[tblSigns]![Open_Work_Order]="yes"
when
[tblHISTORY]![Urgency]={"High","Medium","Low"}

You really do not need to store the Yes/No in [tblSigns]![Open_Work_Order] instead in your query wherein [tblHISTORY]![Urgency] is present, in a calculated field:

Expr1: IIF((([tblHISTORY]![Urgency]="High") OR ([tblHISTORY]![Urgency]="Medium") OR ([tblHISTORY]![Urgency]="Low")), "Yes", "No")

Change Expr1: to whatever you want the field name to be.
Bind your text control to the calculated field.

Next, I would pull your text "high"...
into a table (normalization) and using only a foreign key reference... from that table... and test against, 1, 2, 3 (say 1 == high, etc..) this way the user cannot mistype the values.

[edunker]

What do you mean by bind your text control to the calculated field?

[mbizup]

Hmm - you're posting these questions both here and on MSDN.

In the interest of general forum etiquette, please don't do that. That tends to turn your solutions into a 'jumbled mess' too (and tends to create extra work for those assisting you), with multiple people helping you out without necessarily knowing what help has already been provided elsewhere.

[edunker]

mbizup, that is exactly what i am looking for. more then one way of getting things done.

[zmbd]

+ Bound control is one where the Control Source property of the control is set to a field within a record source such as a stored query or table. You will see this in the control on the form in design view, it will say - [field name] << such as [User_ID] >>

+ UnBound control is one where the Control Source property of the control is Null/Empty. You will see this in the control on the form in design view, it will say - "unbound"

+ Calculated control is one where the Control Source property of the control is to an equation involving the record source or a user-defined-function (UDF). You will see this in the control on the form in design view, it will say for example [=UDF([fieldname])] or [=iif([fieldname],true,false)]

>> Yes, cross-posting isn't considered to be the best form. We do understand the desire to get help quickly in urgent situations; however, quite often, the same experts are working in multiple forums so you really do not gain a whole lot in that aspect - at one point I had a few active accounts on various sites, I've really since dropped them as most of the time the answer shows up here :) - the membership may vary a bit. :)