Link Subform to Subform

[David]

Hello,

I've read several posts which indicate a straightforward method of linking a
subform to a subform:

1. Place an unbound text field on Parent Form.
2. In Subform1, place code in the ON CURRENT event, which populates the
Parent text field with desired data.
3. In Subform2, link desired Child field to unbound text field on Parent form.

I do see the data displayed in the Parent form.

The issue is this: When I click on Subform2 when the Parent form is open,
and open properties, I have the options under the DATA tab, to click on the
ellipsis next to LINK CHILD FIELDS and LINK MASTER FIELDS, which brings up
the SUBFORM FIELD LINKER. However, the unbound text field I added to the
Parent form is not in this drop down list, so I can't create the desired
link!!!

Any ideas?

 

[Dirk Goldgar]

Hello,

I've read several posts which indicate a straightforward method of linking
a
subform to a subform:

1. Place an unbound text field on Parent Form.
2. In Subform1, place code in the ON CURRENT event, which populates the
Parent text field with desired data.
3. In Subform2, link desired Child field to unbound text field on Parent
form.

I do see the data displayed in the Parent form.

The issue is this: When I click on Subform2 when the Parent form is open,
and open properties, I have the options under the DATA tab, to click on
the
ellipsis next to LINK CHILD FIELDS and LINK MASTER FIELDS, which brings up
the SUBFORM FIELD LINKER. However, the unbound text field I added to the
Parent form is not in this drop down list, so I can't create the desired
link!!!

Have you tried just entering the name of the unbound control on the Link
Master Field property line, bypassing the Linker entirely?

 

[Gina Whipp]

David,

This is true, you must manually type it in and you will get your desired
results. The 'linking' does not recognize fields only recordsources and
since your unbound form has no recordsource as far as it's concerned....
what are you trying to link to?

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

 

[David]

Thanks. That seems to work for Integer type fields, but not for text
fields. When I use text fields, it seems to "freeze up" or try to scroll
through subform B, looking for a match. By "scroll through", I mean the
screen seems to be cycling, as it does fast refreshes.

Any ideas why that is?

 

[David]

Thanks. That seems to work for Integer type fields, but not for text
fields. When I use text fields, it seems to "freeze up" or try to scroll
through subform B, looking for a match. By "scroll through", I mean the
screen seems to be cycling, as it does fast refreshes.

Any ideas why that is?

 

[Gina Whipp]

David,

Got a little busy...

Is it text to text? Confirm that it is...

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

 

[Dirk Goldgar]

Thanks. That seems to work for Integer type fields, but not for text
fields. When I use text fields, it seems to "freeze up" or try to scroll
through subform B, looking for a match. By "scroll through", I mean the
screen seems to be cycling, as it does fast refreshes.

Any ideas why that is?

No, I don't expect such behavior. Are you sure you aren't dealing with a
lookup field?

 

[David]

Yes...

Parent Form: A text box control references a field from Subform B. The
field referenced is a drop down box, and I am grabbing column 0. The source
of the drop down is a table, with a AutoID field and string field. The
string field contains a text value, such as 2003-2004 or 2004-2005.

Subform A: Displays a field I built in a query, and the query is the data
source for this subform. This field contains a text string, such as
2003-2004 or 2004-2005.
Thanks,

 

[David]

Yes...

Parent Form: A text box control references a field from Subform B. The
field referenced is a drop down box, and I am grabbing column 0. The source
of the drop down is a table, with a AutoID field and string field. The
string field contains a text value, such as 2003-2004 or 2004-2005.

Subform A: Displays a field I built in a query, and the query is the data
source for this subform. This field contains a text string, such as
2003-2004 or 2004-2005.

 

[Gina Whipp]

If it's a combo box that you are grabbing from then if you have more then
one column you need to link via the bound column. Because it sounds like
column 1 is an AutoNumber and column two is Text. This being the case you
might be linking via AutoNumer to Text. I hope I explained this clearly.

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

 

[Dirk Goldgar]

Yes...

Parent Form: A text box control references a field from Subform B. The
field referenced is a drop down box, and I am grabbing column 0. The
source
of the drop down is a table, with a AutoID field and string field. The
string field contains a text value, such as 2003-2004 or 2004-2005.

Subform A: Displays a field I built in a query, and the query is the data
source for this subform. This field contains a text string, such as
2003-2004 or 2004-2005.

Hmm. I need lots more information. Please post the following:

(1) the names of all objects involved

(2) the RowSource, ColumnCount, BoundColumn, and ControlSource of the combo
box. It is a combo box, right, not a drop-down list box (which is a
different control used on Data Access Pages)?

(3) The field types of the table that is the combo box's RowSource

(4) the ControlSource of the text box (on the parent form) that is pulling
the value from the combo box

(5) the RecordSource of the form object that is being displayed by "Subform
B", and the field type (from the table design) of the field in that
recordsource to which the combo box is bound

(6) the RecordSource of the form object that is being displayed by "Subform
A"

(7) the Link Master Fields and Link Child Fields properties of both
subforms.

(8) the version and SP-level of Access that you are using.

I'm sorry for asking for so much information, but you're describing behavior
that I can't account for with the information you've posted so far.