LinkMasterFields property setting

[casih]

I am fairly new to access. I am creating a form "Case details" within that
form i Have inserted a sub form "Meetings". I have defined relationships
between the tables which in this case the link is [CaseNumber]. For some
reason every time i try and input data into the subform I recieve the message
"The LinkMasterFields property setting has produced this error: 'Procedure
declaration does not match description of event or procedure having the same
name"

Help!

 

[KARL DEWEY]

Did you set a one-to-many relationship using the [CaseNumber] fields of the
two tables?
Did you select Referential Integerity and Cascade Update for that
relationship?

 

[casih]

Yes! the thing that gets me it was working fine before!

Did you set a one-to-many relationship using the [CaseNumber] fields of the
two tables?
Did you select Referential Integerity and Cascade Update for that
relationship?

--
Build a little, test a little.

I am fairly new to access. I am creating a form "Case details" within that
form i Have inserted a sub form "Meetings". I have defined relationships
between the tables which in this case the link is [CaseNumber]. For some
reason every time i try and input data into the subform I recieve the message
"The LinkMasterFields property setting has produced this error: 'Procedure
declaration does not match description of event or procedure having the same
name"

Help!

 

[KARL DEWEY]

Post the SQL of queries used for both forms.
--
Build a little, test a little.

Yes! the thing that gets me it was working fine before!

Did you set a one-to-many relationship using the [CaseNumber] fields of the
two tables?
Did you select Referential Integerity and Cascade Update for that
relationship?

--
Build a little, test a little.

I am fairly new to access. I am creating a form "Case details" within that
form i Have inserted a sub form "Meetings". I have defined relationships
between the tables which in this case the link is [CaseNumber]. For some
reason every time i try and input data into the subform I recieve the message
"The LinkMasterFields property setting has produced this error: 'Procedure
declaration does not match description of event or procedure having the same
name"

Help!

 

[casih]

Hi,

I just added the forms as a sub form without setting up any SQLs - what
should I have done?

Post the SQL of queries used for both forms.
--
Build a little, test a little.

Yes! the thing that gets me it was working fine before!

Did you set a one-to-many relationship using the [CaseNumber] fields of the
two tables?
Did you select Referential Integerity and Cascade Update for that
relationship?

--
Build a little, test a little.


:

I am fairly new to access. I am creating a form "Case details" within that
form i Have inserted a sub form "Meetings". I have defined relationships
between the tables which in this case the link is [CaseNumber]. For some
reason every time i try and input data into the subform I recieve the message
"The LinkMasterFields property setting has produced this error: 'Procedure
declaration does not match description of event or procedure having the same
name"

Help!

 

[KARL DEWEY]

The subform has to be bound to your table. The best way is through a query.

I asked that you post the SQL of that query which can be created using the
wizard, design view, or SQL view.

--
Build a little, test a little.

Hi,

I just added the forms as a sub form without setting up any SQLs - what
should I have done?

Post the SQL of queries used for both forms.
--
Build a little, test a little.

Yes! the thing that gets me it was working fine before!

:

Did you set a one-to-many relationship using the [CaseNumber] fields of the
two tables?
Did you select Referential Integerity and Cascade Update for that
relationship?

--
Build a little, test a little.


:

I am fairly new to access. I am creating a form "Case details" within that
form i Have inserted a sub form "Meetings". I have defined relationships
between the tables which in this case the link is [CaseNumber]. For some
reason every time i try and input data into the subform I recieve the message
"The LinkMasterFields property setting has produced this error: 'Procedure
declaration does not match description of event or procedure having the same
name"

Help!

 

[John W. Vinson]

I just added the forms as a sub form without setting up any SQLs - what
should I have done?

If you used the forms wizard, Access set up the queries for you. Open the
subform in design view; view its Properties; find the "Record Source"
property, first on the Data tab; if it's a query click the ... icon by it and
use View... SQL to find the query text to post here.

 

[casih]

The record source is just showing as Meeting and their is no query linked to
it. what should the query say?

 

[casih]

also every other sub form i am putting into the case details form is
producing the same error message. so is the problem with case details?

tHis the code i get from that form:
SELECT [Case Details].*, [Member Details].FirstName, [Member
Details].Surname, Workplace.WorkPlaceCode, Workplace.WorkpName
FROM ([Member Details] INNER JOIN [Case Details] ON [Member
Details].MembershipNumber = [Case Details].MembershipNumber) INNER JOIN
Workplace ON [Member Details].MembershipNumber = Workplace.MembershipNumber;

 

[casih]

Now its saying that the Case Form is not updateable - ARGGGGGHHHHHHHHH is
this all linked?

also every other sub form i am putting into the case details form is
producing the same error message. so is the problem with case details?

tHis the code i get from that form:
SELECT [Case Details].*, [Member Details].FirstName, [Member
Details].Surname, Workplace.WorkPlaceCode, Workplace.WorkpName
FROM ([Member Details] INNER JOIN [Case Details] ON [Member
Details].MembershipNumber = [Case Details].MembershipNumber) INNER JOIN
Workplace ON [Member Details].MembershipNumber = Workplace.MembershipNumber;

The record source is just showing as Meeting and their is no query linked to
it. what should the query say?

 

[John W. Vinson]

also every other sub form i am putting into the case details form is
producing the same error message. so is the problem with case details?

tHis the code i get from that form:
SELECT [Case Details].*, [Member Details].FirstName, [Member
Details].Surname, Workplace.WorkPlaceCode, Workplace.WorkpName
FROM ([Member Details] INNER JOIN [Case Details] ON [Member
Details].MembershipNumber = [Case Details].MembershipNumber) INNER JOIN
Workplace ON [Member Details].MembershipNumber = Workplace.MembershipNumber;

Almost surely this is the cause of the problem. Multitable queries can be
updateable, but the more tables you have the less likely it will be; different
versions of Access have changed the rules for what's updateable and what's
not.

I don't know the structure of your database or your form, but *typically* (not
universally) you would use only one table per form/subform. If you just want
to display the member name and workplace on the Case Details subform, you may
want to consider using a combo box bound to the MembershipNumber but
displaying the member information.

 

[casih]

I have one main form Case Details and various sub forms and its all gone to
pot. I havent got a clue what I have done as it was all working fine then
this!! I am tempted just to start again but worried that I will just come up
with the same errors further down the line! Is there any chance you would
have a look at it if i emailed it over?

also every other sub form i am putting into the case details form is
producing the same error message. so is the problem with case details?

tHis the code i get from that form:
SELECT [Case Details].*, [Member Details].FirstName, [Member
Details].Surname, Workplace.WorkPlaceCode, Workplace.WorkpName
FROM ([Member Details] INNER JOIN [Case Details] ON [Member
Details].MembershipNumber = [Case Details].MembershipNumber) INNER JOIN
Workplace ON [Member Details].MembershipNumber = Workplace.MembershipNumber;

Almost surely this is the cause of the problem. Multitable queries can be
updateable, but the more tables you have the less likely it will be; different
versions of Access have changed the rules for what's updateable and what's
not.

I don't know the structure of your database or your form, but *typically* (not
universally) you would use only one table per form/subform. If you just want
to display the member name and workplace on the Case Details subform, you may
want to consider using a combo box bound to the MembershipNumber but
displaying the member information.

 

[casih]

Its all gone to pot. I am tempted to start again bit have put a lot of work
into this and am not sure if I wont hot these problems again!! arrgggh. Is
there any chance you would be able to have a quick scan at it if enail it
over to you?

also every other sub form i am putting into the case details form is
producing the same error message. so is the problem with case details?

tHis the code i get from that form:
SELECT [Case Details].*, [Member Details].FirstName, [Member
Details].Surname, Workplace.WorkPlaceCode, Workplace.WorkpName
FROM ([Member Details] INNER JOIN [Case Details] ON [Member
Details].MembershipNumber = [Case Details].MembershipNumber) INNER JOIN
Workplace ON [Member Details].MembershipNumber = Workplace.MembershipNumber;

Almost surely this is the cause of the problem. Multitable queries can be
updateable, but the more tables you have the less likely it will be; different
versions of Access have changed the rules for what's updateable and what's
not.

I don't know the structure of your database or your form, but *typically* (not
universally) you would use only one table per form/subform. If you just want
to display the member name and workplace on the Case Details subform, you may
want to consider using a combo box bound to the MembershipNumber but
displaying the member information.

 

[John W. Vinson]

I have one main form Case Details and various sub forms and its all gone to
pot. I havent got a clue what I have done as it was all working fine then
this!! I am tempted just to start again but worried that I will just come up
with the same errors further down the line! Is there any chance you would
have a look at it if i emailed it over?

I'm a self-employed computer consultant, donating my time for free on these
groups. Studying private databases would normally be reserved to paying
customers.

Did you - perhaps - try my suggestion of using a mainform with subforms? The
problem IS that your form's recordsource query is not updateable. if you fix
the query you will fix the form, and it's (usually) not necessary or
appropriate to have a form based on a multitable query.