Access Event when TextBox is populated from another form
Hi
I have a text box called LicenceNumber that is populated programmatically from another form using the following code. What is the best even behind the text box LicenceNumber that will be triggered when text is changed from the other form?
Forms(oNewLicenseeFor).Con
I have a text box called LicenceNumber that is populated programmatically from another form using the following code. What is the best even behind the text box LicenceNumber that will be triggered when text is changed from the other form?
Forms(oNewLicenseeFor).Con
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
John Tsioumpris
I think Before Update should be the one you want
Alternatively, make the event PUBLIC, and then you can call it e.g.:
Forms(oNewLicenseeFor).Controls("LicenceNumber").Text = Nz(DMax("LicenceNumberPK", "t_Licence"), 0)
call Forms(oNewLicenseeFor).licensenumber_AfterUpdate
For some reason, the other three experts let this slide but the real problem is storing the licenseNumber in two places. It is time to review your schema and normalize it. Not to mention the fact that if the other form isn't open, you will get an error. Forms don't store data. Tables store data and each piece of data belongs in one and only one table. The only "data" that ever appears in multiple places is foreign keys since they are the glue that connect the tables to each other.
Maybe he's just displaying it....
Jim.
Jim.
ASKER
I am just displaying it
ASKER
Thanks very much
<<I am just displaying it>>
Couple suggestions then to avoid the database hit:
1. In the called form, refer back to your other form(s) and just grab the values you need if they are used (assumes they are open of course).
2. Pass the value into the form using the OpenArgs argument. While OpenArgs is a single property, one way to pass in multiple things is to use a delimiter and use a TAG + VALUE approach. i.e.
60 DoCmd.OpenForm "frmEmployers", acNormal, , , acFormEdit, acDialog, "FORMMODE=ADD;SETCTRLTODAT
Here I'm calling a pop-up form from a Not In List event to add an employer. So I want the form to be in add mode, the control txtName to be set what was in the list, and when the form is done, come back to frmPatients.
The called form looks at OpenArgs, see's the tag SETCTRLTODATA, and calls this routine:
Sub SetControlsToData(frm As Form, strData As String)
' Set controls on frm to values contained in strData.
' Delimiter is a ":". Format of strData is control name: value.
Dim intPairNumber As Integer
Dim varControlName As Variant
Dim varData As Variant
10 intPairNumber = 1
20 Do
30 varControlName = dhExtractString(strData, intPairNumber, ":")
40 If varControlName = "" Then Exit Do
50 varData = dhExtractString(strData, intPairNumber + 1, ":")
60 frm(varControlName) = varData
70 intPairNumber = intPairNumber + 2
80 Loop
End Sub
This is just one way you could do something like this and there are any number of schemes you could come up with. But open args is a great way of passing data and avoid going back out to disk.
HTH,
Jim.
Couple suggestions then to avoid the database hit:
1. In the called form, refer back to your other form(s) and just grab the values you need if they are used (assumes they are open of course).
2. Pass the value into the form using the OpenArgs argument. While OpenArgs is a single property, one way to pass in multiple things is to use a delimiter and use a TAG + VALUE approach. i.e.
60 DoCmd.OpenForm "frmEmployers", acNormal, , , acFormEdit, acDialog, "FORMMODE=ADD;SETCTRLTODAT
Here I'm calling a pop-up form from a Not In List event to add an employer. So I want the form to be in add mode, the control txtName to be set what was in the list, and when the form is done, come back to frmPatients.
The called form looks at OpenArgs, see's the tag SETCTRLTODATA, and calls this routine:
Sub SetControlsToData(frm As Form, strData As String)
' Set controls on frm to values contained in strData.
' Delimiter is a ":". Format of strData is control name: value.
Dim intPairNumber As Integer
Dim varControlName As Variant
Dim varData As Variant
10 intPairNumber = 1
20 Do
30 varControlName = dhExtractString(strData, intPairNumber, ":")
40 If varControlName = "" Then Exit Do
50 varData = dhExtractString(strData, intPairNumber + 1, ":")
60 frm(varControlName) = varData
70 intPairNumber = intPairNumber + 2
80 Loop
End Sub
This is just one way you could do something like this and there are any number of schemes you could come up with. But open args is a great way of passing data and avoid going back out to disk.
HTH,
Jim.
ASKER
thanks very much Jim