469,277 Members | 2,357 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,277 developers. It's quick & easy.

A97 changes the link child and link master fields on a subform control w/o consulting or informing me

MLH
I have a subform control on a mainform. Each time I do anything
experimentally with it - like even change its Width property, A97
takes the liberty of setting values in the link child field and link
master field to a common field value. This is happening, I suppose,
because I have purposefully left the two property settings empty.

I'm just using the unbound subform control as a glorified list box.

Can I prevent this undesirable behavior?
Jan 12 '06 #1
4 1959

"MLH" <CR**@NorthState.net> wrote in message
news:1g********************************@4ax.com...
I have a subform control on a mainform. Each time I do anything
experimentally with it - like even change its Width property, A97
takes the liberty of setting values in the link child field and link
master field to a common field value. This is happening, I suppose,
because I have purposefully left the two property settings empty.

I'm just using the unbound subform control as a glorified list box.

Can I prevent this undesirable behavior?


Yes, I agree that sometimes, in its attempts to be helpful, sometimes Access
can be TOO helpful. All I can suggest is check the settings in Tools |
Options to see if there is something which might apply -- offhand, I do not
recall one for LinkMaster and LinkChild autofill, however.

You may be stuck with going in manually and clearing those Properties when
you make a change to the Form embedded in the Subform Control or to the
Subform Control.

A workaround that would suggest itself to me would be to change the name of
one or the other of those Fields, so the association will not automatically
be made.

Larry Linson
Microsoft Access MVP

Jan 12 '06 #2
MLH
Yes, I agree that sometimes, in its attempts to be helpful, sometimes Access
can be TOO helpful. All I can suggest is check the settings in Tools |
Options to see if there is something which might apply -- offhand, I do not
recall one for LinkMaster and LinkChild autofill, however.

You may be stuck with going in manually and clearing those Properties when
you make a change to the Form embedded in the Subform Control or to the
Subform Control.

A workaround that would suggest itself to me would be to change the name of
one or the other of those Fields, so the association will not automatically
be made.

As always, you dig deep. Thx for sharing your thoughts. I'd take you
up on the work-around if it weren't for the fact that I'm pretty much
done with the form now. The infrequency of the problem is sufficient
to make it a minor concern.
Jan 13 '06 #3
In six months time when you go back to that form to update/fix something you
may well have forgotten that this will happen.

Just stick some code in the form load event to set the Linkmaster and
LinkChild properties to empty strings and your done with it.

e,g,
Private Sub Form_Load()
With Me.subformcontrolnamehere
.LinkChildFields = ""
.LinkMasterFields = ""
End With
End Sub

--

Terry Kreft
"MLH" <CR**@NorthState.net> wrote in message
news:4g********************************@4ax.com...
Yes, I agree that sometimes, in its attempts to be helpful, sometimes Accesscan be TOO helpful. All I can suggest is check the settings in Tools |
Options to see if there is something which might apply -- offhand, I do notrecall one for LinkMaster and LinkChild autofill, however.

You may be stuck with going in manually and clearing those Properties whenyou make a change to the Form embedded in the Subform Control or to the
Subform Control.

A workaround that would suggest itself to me would be to change the name ofone or the other of those Fields, so the association will not automaticallybe made.

As always, you dig deep. Thx for sharing your thoughts. I'd take you
up on the work-around if it weren't for the fact that I'm pretty much
done with the form now. The infrequency of the problem is sufficient
to make it a minor concern.

Jan 13 '06 #4
MLH
On Fri, 13 Jan 2006 13:23:48 -0000, "Terry Kreft"
<te*********@mps.co.uk> wrote:
In six months time when you go back to that form to update/fix something you
may well have forgotten that this will happen.

6 months my Ass! Try 6 minutes. Great idea - many thanks.
Jan 14 '06 #5

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

2 posts views Thread by Deborah V. Gardner | last post: by
2 posts views Thread by Chewy1026 via AccessMonster.com | last post: by
reply views Thread by zhoujie | last post: by
reply views Thread by suresh191 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.