LinkMasterFields Property Setting

[AMcShea]

I'm working on a form that has subforms in it. When I try to go to another
record on the form, I get this error:
"The linkmasterfields property setting has produced this error: 'Ambiguous
name detected Add_Record_Click"

Anyone know what it means?
Thanks

 

[strive4peace]

it sounds like you have removed the PRIVATE keyword from the front of
the procedure declaration OR you have 2 procedures behind the form with
the same name

'~~~~~~~~~ Compile ~~~~~~~~~

Whenever you change code or references, your should always compile
before executing.

from the menu in a VBE (module) window: Debug, Compile

fix any errors on the yellow highlighted lines

keep compiling until nothing happens (this is good!)


Warm Regards,
Crystal

Access Basics
8-part free tutorial that covers essentials in Access
http://www.accessmvp.com/Strive4Peace/Index.htm

*
have an awesome day
*

 

[John W. Vinson]

I'm working on a form that has subforms in it. When I try to go to another
record on the form, I get this error:
"The linkmasterfields property setting has produced this error: 'Ambiguous
name detected Add_Record_Click"

Anyone know what it means?
Thanks

It means that your Form's Module has two functions named Add_Record_Click.
Open the form in design view and search for Private Sub Add_Record_Click -
there must be two Subs of that name. Keep the one that is in use and delete
the other one.

I'd also put

Option Explicit

above the very first line of the module, and select Debug... Compile <your
project>. If you have this error, exposed when compile-on-demand runs, it's
very likely you have more.

 

[AMcShea]

Thanks both suggestions worked.
--
AKM

It means that your Form's Module has two functions named Add_Record_Click.
Open the form in design view and search for Private Sub Add_Record_Click -
there must be two Subs of that name. Keep the one that is in use and delete
the other one.

I'd also put

Option Explicit

above the very first line of the module, and select Debug... Compile <your
project>. If you have this error, exposed when compile-on-demand runs, it's
very likely you have more.