Ah, ok.
We don't want to actually "copy" the data to field in the main form (as this
would make maintains impossible). If you were to edit a destinations in the
sub-form, (or even by code, or sql updates, then the system would have to
"know" to copy the data to the field in the main table. This breaks nearly
every relational database rule in the world. (and, makes the data editing
impossible). Just deleting a record in sub-form would mean that special code
has to run, and re-update the text box in the main table.
However, we most certainly can *display* this information in a text box on
the main form (but, as mentioned, copy data?..no, do NOT do that!!).
For the particular form, you could write a function like:
Public Function ShowDest() As String
Dim rst As DAO.Recordset
Dim strText As String
Set rst = Me.child1.Form.RecordsetClone
If rst.RecordCount > 0 Then
rst.MoveFirst
Do While rst.EOF = False
If strText <> "" Then
strText = strText & ","
End If
strText = strText & rst!desc
rst.MoveNext
Loop
End If
Set rst = Nothing
ShowDest = strText
End Function
Then, simply place a un-bound text box on the main form, and then set the
data source of that text box to the above function
=ShowDest()
The above will thus do what you want.....
If you don't actually have a sub-form in the particular form, then you left
that detail out, but the above code can be modified to deal with this.
Of course, you change the name of the above field name used, and sub-form
name used to whatever you used....
So, the nice thing about the above solution is that if you change, or
delete, or edit the values in the sub-form data, then you don't have to run
special code to display the list as above.
Get the above working. You likely may have to add some code to "refresh" the
list during editing the sub-form data. get the base code working, and then
we can move on to having the display updated correctly *DURING* editing of
the sub-form.