Can't build a link between unbound forms error

[Fred Wildauer]

I have inserted a new form into an existing form and I am
receiving this error whenever I attempt to link the master
with the child - "Can't build a link between unbound forms
error". I have created a relationalship between both forms
and I have attempted to compare the properties of this
form to some of the existing subforms, but I have not been
able to find any differences.

Does anyone have any thoughts?

Thank you!

Fred

 

[John Vinson]

I have inserted a new form into an existing form and I am
receiving this error whenever I attempt to link the master
with the child - "Can't build a link between unbound forms
error". I have created a relationalship between both forms
and I have attempted to compare the properties of this
form to some of the existing subforms, but I have not been
able to find any differences.

You can't build a relationship between unbound forms - simple as that.

If the Forms have no recordsource, then there are no table fields to
serve as the Master Link Field and Child Link Field. You cannot create
a "relationship" between forms; a Form is just a window onto data. You
can create a relationship between two Tables, and then bind the forms
to those Tables - perhaps that's what you've done in the working form.

 

[Fred Wildauer]

There lies the problem! The form that I attempting to
insert is indeed bound to a table that has a field that
should allow me to link to the master. The only thing I
can think of is that there is no data in the new table and
some how this is causing the error.

 

[Rick Brandt]

There lies the problem! The form that I attempting to
insert is indeed bound to a table that has a field that
should allow me to link to the master. The only thing I
can think of is that there is no data in the new table and
some how this is causing the error.

First, it's not exactly true that you can't create this link between
unbound forms. The Main form can be unbound. You just can't use the wizard
invoked from the build [...] button to create the link. You have to type
the MasterLink and ChildLink properties in manually.

Second, I suspect that a form can get corrupted and cause this error when
the form is in fact bound because I have seen it reported numerous times in
these groups and vaguely recall seeing it myself some time back. I would
try the compact/decompile/compact/recompile/compact routine on a copy of
your file and see if the problem goes away. You might also try making a
copy of the form itself to see if the copy reacts the same way.

When the main form is in fact bound you might be able to get it working by
typing the link values in manually as when the main form is not bound, but
I would still treat the form as suspect as long as it does this.

 

[Fred Wildauer]

I did try this earlier - but I receive an error because
the field I am linking to is an Autonumber field -
<<COVID>>. The error I receive is as follows: "The
LinkMasterFields property has produced this error. "The
object doesn't contain the Automatiion object COVID"."

Any thoughts on what I should do now??

Fred

-----Original Message-----

There lies the problem! The form that I attempting to
insert is indeed bound to a table that has a field that
should allow me to link to the master. The only thing I
can think of is that there is no data in the new table and
some how this is causing the error.

First, it's not exactly true that you can't create this link between
unbound forms. The Main form can be unbound. You just can't use the wizard
invoked from the build [...] button to create the link. You have to type
the MasterLink and ChildLink properties in manually.

Second, I suspect that a form can get corrupted and cause this error when
the form is in fact bound because I have seen it reported numerous times in
these groups and vaguely recall seeing it myself some time back. I would
try the compact/decompile/compact/recompile/compact routine on a copy of
your file and see if the problem goes away. You might also try making a
copy of the form itself to see if the copy reacts the same way.

When the main form is in fact bound you might be able to get it working by
typing the link values in manually as when the main form is not bound, but
I would still treat the form as suspect as long as it does this.


--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com




.

 

[Rick Brandt]

I did try this earlier - but I receive an error because
the field I am linking to is an Autonumber field -
<<COVID>>. The error I receive is as follows: "The
LinkMasterFields property has produced this error. "The
object doesn't contain the Automatiion object COVID"."

Any thoughts on what I should do now??

Does COVID exist only in the underlying table or do you also have a control
on the form bound to it? If there is a bound control using COVID as its
ControlSource does it have a name other than "COVID"? You might try using
the name of the control rather than the field (or make them the same).