Populate field

[sweetiepie]

I have a field txtSource that I would like to be populated based on what a user selects from the cboFrom field. TxtSource is an unbound field on the form.

If "Home" is selected from cboFrom I would like for txtSource to be populated with the word home. Otherwise I would like txtSouce to equal what has been entered in txtOrigin (which is a bound field)

What code to write or where to insert it....in the form or in the cboFrom combo box. Please help

[Missinglinq]

Place this code in the Code Module for your Form:

Private Sub cboFrom_AfterUpdate()
 If Me.cboFrom = "Home" Then
  Me.txtSource = "Home"
 Else
  Me.txtSource = Me.txtOrigin
 End If
End Sub


Private Sub txtOrigin_AfterUpdate()
 If Me.cboFrom = "Home" Then
  Me.txtSource = "Home"
 Else
  Me.txtSource = Me.txtOrigin
 End If
End Sub


Private Sub Form_Current()
 If Me.cboFrom = "Home" Then
  Me.txtSource = "Home"
 Else
  Me.txtSource = Me.txtOrigin
 End If
End Sub

Linq ;0)>

[sweetiepie]

Do I need to place the code in all three places? Sorry I'm new to coding so I just wanted to be sure.

[Missinglinq]

Yes; the Values of both cboFrom and txtOrigin are involved here, and you have no way of knowing which will be populated first, or even if both will be populated, hence the code in both of these AfterUpdate events. And since txtSource is Unbound, you have to have code in the Form_Current event to do the evaluation each time you move to a given Record, in order for txtSource to be appropriate to that given Record.

I should have noted before that this will only work if the Form in question is a Single View Form, i.e. one where you can only view one Record at a time. If it is a Continuous View or Datasheet View Form, another method will be needed to do this same thing. In that case you'd need to use the Control Source of the txtSource Textbox, and enter this in the Property box

=IIf([cboFrom]="Home",[cboFrom],[txtOrigin])

You could actually use this for any type of Form, but I tend to stay away from using the IIF() function, unless nothing else will work. IIF() can have unexpected results, at times, so personally I just avoid it. Your choice!

Linq ;0)>