synching subforms - The object doesn't contain the Automation obje

E

efandango

I want to be able to link a continuous form to another continous form/subform
(but not contained withing the master form). Access will not allow me to do
this, but I was wondering if there was a manual/pseudo way of doing this?

I have managed to link/synch the two forms, but when I try to create a new
record by using any of the fields on the ‘sub form’, I get this pop-up error
message:
The object doesn't contain the Automation object
'tbl_Road_Restrictions_Detail.

You tried to run a Visual Basic procedure to set a property for and object.
However, the component doesn't make the property or method available for
Automation operations.

But when I say OK to the error box, it still allows me to fill in the fields
and create the record. I want to fix this problem, but don’t know how. (I’m
not even sure what the error means)
The two tables are below and are [Linked by Road_Restriction_ID]. Can
someone give me some idea(s) on how to resolve this?

Table Structures
tbl_Road_Restrictions
Road_Restriction_ID AutoNumber
Road_Name_From Text
Road_Name_To Text
Restriction Text
Run_No Number
Direction_From Text
Direction_To Text
Junction_ID Number

tbl_Road_Restrictions_Detail
Road_Restriction_Detail_ID AutoNumber
Road_Restriction_ID Number
Run_Direction Text
Run_waypoint Text
Postcode Text
Run_No Number



Form Structures

frm_Road_Restrictions
Link Master Fields: [Run_No]
LinkChild Fields: [Run_No]
Record Source: tbl_Road_Restrictions


frm_Road_Restrictions_Detail
Link Master Fields:
Forms![frm_Runs]![frm_Road_Restrictions].Form![Road_Restriction_ID]
LinkChild Fields: [Road_Restriction_ID]

Record Source:
SELECT tbl_Road_Restrictions_Detail.Road_Restriction_Detail_ID,
tbl_Road_Restrictions_Detail.Road_Restriction_ID,
tbl_Road_Restrictions_Detail.Run_Direction,
tbl_Road_Restrictions_Detail.Run_waypoint FROM tbl_Road_Restrictions INNER
JOIN tbl_Road_Restrictions_Detail ON
tbl_Road_Restrictions.Road_Restriction_ID=tbl_Road_Restrictions_Detail.Road_Restriction_ID;


The two tables are below (Linked by Road_Restriction_ID).
Can someone give me some idea(s) on how to achieve this?

The object doesn't contain the Automation object
'tbl_Road_Restrictions_Detail.

You tried to run a Visual Basic procedure to set a property for and object.
However, the component doesn't make the property or method available for
Automation operations.
 
E

Evi

I guess Access is trying to protect us from the aesthetically ugly results
of putting a subform into a main form :)
You haven't given the visual basic you have used to 'sync the 2 forms' so I
can't comment on your error message.
One thing, you've only mentioned 1 record source for both forms, maybe this
was just to save space. The usual structure would be to have a main form
based on tblRoadRestriction (or on a query based on that table and the
subform based on tbl (or query) RoadRestrictionDetails. They would then by
linked by RoadRestrictionID
Evi
efandango said:
I want to be able to link a continuous form to another continous form/subform
(but not contained withing the master form). Access will not allow me to do
this, but I was wondering if there was a manual/pseudo way of doing this?

I have managed to link/synch the two forms, but when I try to create a new
record by using any of the fields on the 'sub form', I get this pop-up error
message:
The object doesn't contain the Automation object
'tbl_Road_Restrictions_Detail.

You tried to run a Visual Basic procedure to set a property for and object.
However, the component doesn't make the property or method available for
Automation operations.

But when I say OK to the error box, it still allows me to fill in the fields
and create the record. I want to fix this problem, but don't know how. (I' m
not even sure what the error means)
The two tables are below and are [Linked by Road_Restriction_ID]. Can
someone give me some idea(s) on how to resolve this?

Table Structures
tbl_Road_Restrictions
Road_Restriction_ID AutoNumber
Road_Name_From Text
Road_Name_To Text
Restriction Text
Run_No Number
Direction_From Text
Direction_To Text
Junction_ID Number

tbl_Road_Restrictions_Detail
Road_Restriction_Detail_ID AutoNumber
Road_Restriction_ID Number
Run_Direction Text
Run_waypoint Text
Postcode Text
Run_No Number



Form Structures

frm_Road_Restrictions
Link Master Fields: [Run_No]
LinkChild Fields: [Run_No]
Record Source: tbl_Road_Restrictions


frm_Road_Restrictions_Detail
Link Master Fields:
Forms![frm_Runs]![frm_Road_Restrictions].Form![Road_Restriction_ID]
LinkChild Fields: [Road_Restriction_ID]

Record Source:
SELECT tbl_Road_Restrictions_Detail.Road_Restriction_Detail_ID,
tbl_Road_Restrictions_Detail.Road_Restriction_ID,
tbl_Road_Restrictions_Detail.Run_Direction,
tbl_Road_Restrictions_Detail.Run_waypoint FROM tbl_Road_Restrictions INNER
JOIN tbl_Road_Restrictions_Detail ON
tbl_Road_Restrictions.Road_Restriction_ID=tbl_Road_Restrictions_Detail.Road_
Restriction_ID;


The two tables are below (Linked by Road_Restriction_ID).
Can someone give me some idea(s) on how to achieve this?

The object doesn't contain the Automation object
'tbl_Road_Restrictions_Detail.

You tried to run a Visual Basic procedure to set a property for and object.
However, the component doesn't make the property or method available for
Automation operations.
 
E

efandango

I have not used any visual basic code to sync the two forms.

I did state in my original post what two table were involved. How they were
linked. I had linked the two forms just like you suggested. I alsoo gave full
details of the table structures. I'm slightly confused by your reply stating
that none of these things were mentioned. Perhaps you didn't get the full
posting?

Evi said:
I guess Access is trying to protect us from the aesthetically ugly results
of putting a subform into a main form :)
You haven't given the visual basic you have used to 'sync the 2 forms' so I
can't comment on your error message.
One thing, you've only mentioned 1 record source for both forms, maybe this
was just to save space. The usual structure would be to have a main form
based on tblRoadRestriction (or on a query based on that table and the
subform based on tbl (or query) RoadRestrictionDetails. They would then by
linked by RoadRestrictionID
Evi
efandango said:
I want to be able to link a continuous form to another continous form/subform
(but not contained withing the master form). Access will not allow me to do
this, but I was wondering if there was a manual/pseudo way of doing this?

I have managed to link/synch the two forms, but when I try to create a new
record by using any of the fields on the 'sub form', I get this pop-up error
message:
The object doesn't contain the Automation object
'tbl_Road_Restrictions_Detail.

You tried to run a Visual Basic procedure to set a property for and object.
However, the component doesn't make the property or method available for
Automation operations.

But when I say OK to the error box, it still allows me to fill in the fields
and create the record. I want to fix this problem, but don't know how. (I' m
not even sure what the error means)
The two tables are below and are [Linked by Road_Restriction_ID]. Can
someone give me some idea(s) on how to resolve this?

Table Structures
tbl_Road_Restrictions
Road_Restriction_ID AutoNumber
Road_Name_From Text
Road_Name_To Text
Restriction Text
Run_No Number
Direction_From Text
Direction_To Text
Junction_ID Number

tbl_Road_Restrictions_Detail
Road_Restriction_Detail_ID AutoNumber
Road_Restriction_ID Number
Run_Direction Text
Run_waypoint Text
Postcode Text
Run_No Number



Form Structures

frm_Road_Restrictions
Link Master Fields: [Run_No]
LinkChild Fields: [Run_No]
Record Source: tbl_Road_Restrictions


frm_Road_Restrictions_Detail
Link Master Fields:
Forms![frm_Runs]![frm_Road_Restrictions].Form![Road_Restriction_ID]
LinkChild Fields: [Road_Restriction_ID]

Record Source:
SELECT tbl_Road_Restrictions_Detail.Road_Restriction_Detail_ID,
tbl_Road_Restrictions_Detail.Road_Restriction_ID,
tbl_Road_Restrictions_Detail.Run_Direction,
tbl_Road_Restrictions_Detail.Run_waypoint FROM tbl_Road_Restrictions INNER
JOIN tbl_Road_Restrictions_Detail ON
tbl_Road_Restrictions.Road_Restriction_ID=tbl_Road_Restrictions_Detail.Road_
Restriction_ID;


The two tables are below (Linked by Road_Restriction_ID).
Can someone give me some idea(s) on how to achieve this?

The object doesn't contain the Automation object
'tbl_Road_Restrictions_Detail.

You tried to run a Visual Basic procedure to set a property for and object.
However, the component doesn't make the property or method available for
Automation operations.
 
B

BruceM

There is no built-in way to nest a continuous form within a continuous form,
if that's what you are trying to do. The link below may have a suitable
workaround.
From your description you have two subforms, but you say they are not
contained within the master form. However, if they are subforms they are by
definition part of a master form. Also, from your description the Details
table is on the many side of a one-to-many with the Road Restrictions table,
which would lead me to expect a form/subform relationship between forms
based on the two tables.
frmRoadRestrictions (actually, the subform control) has Link Child and Link
Master fields set to Run_No, which means there must be a master form you
have not described with a record source you have not described, that has
Run_No as a primary key, or at least as a field.
To what end do you wish to link the forms? What exactly do you mean by
"link"?
If you are asking for a workaround on the restriction against a subform
within a continuous subform, there are some possibilities here:
http://www.daiglenet.com/msaccess.htm
Look for the Synch Continuous Combo link.
A Google groups search may turn up additional ideas.

efandango said:
I have not used any visual basic code to sync the two forms.

I did state in my original post what two table were involved. How they
were
linked. I had linked the two forms just like you suggested. I alsoo gave
full
details of the table structures. I'm slightly confused by your reply
stating
that none of these things were mentioned. Perhaps you didn't get the full
posting?

Evi said:
I guess Access is trying to protect us from the aesthetically ugly
results
of putting a subform into a main form :)
You haven't given the visual basic you have used to 'sync the 2 forms' so
I
can't comment on your error message.
One thing, you've only mentioned 1 record source for both forms, maybe
this
was just to save space. The usual structure would be to have a main form
based on tblRoadRestriction (or on a query based on that table and the
subform based on tbl (or query) RoadRestrictionDetails. They would then
by
linked by RoadRestrictionID
Evi
efandango said:
I want to be able to link a continuous form to another continous form/subform
(but not contained withing the master form). Access will not allow me
to do
this, but I was wondering if there was a manual/pseudo way of doing
this?

I have managed to link/synch the two forms, but when I try to create a
new
record by using any of the fields on the 'sub form', I get this pop-up error
message:
The object doesn't contain the Automation object
'tbl_Road_Restrictions_Detail.

You tried to run a Visual Basic procedure to set a property for and object.
However, the component doesn't make the property or method available
for
Automation operations.

But when I say OK to the error box, it still allows me to fill in the fields
and create the record. I want to fix this problem, but don't know how.
(I' m
not even sure what the error means)
The two tables are below and are [Linked by Road_Restriction_ID]. Can
someone give me some idea(s) on how to resolve this?

Table Structures
tbl_Road_Restrictions
Road_Restriction_ID AutoNumber
Road_Name_From Text
Road_Name_To Text
Restriction Text
Run_No Number
Direction_From Text
Direction_To Text
Junction_ID Number

tbl_Road_Restrictions_Detail
Road_Restriction_Detail_ID AutoNumber
Road_Restriction_ID Number
Run_Direction Text
Run_waypoint Text
Postcode Text
Run_No Number



Form Structures

frm_Road_Restrictions
Link Master Fields: [Run_No]
LinkChild Fields: [Run_No]
Record Source: tbl_Road_Restrictions


frm_Road_Restrictions_Detail
Link Master Fields:
Forms![frm_Runs]![frm_Road_Restrictions].Form![Road_Restriction_ID]
LinkChild Fields: [Road_Restriction_ID]

Record Source:
SELECT tbl_Road_Restrictions_Detail.Road_Restriction_Detail_ID,
tbl_Road_Restrictions_Detail.Road_Restriction_ID,
tbl_Road_Restrictions_Detail.Run_Direction,
tbl_Road_Restrictions_Detail.Run_waypoint FROM tbl_Road_Restrictions
INNER
JOIN tbl_Road_Restrictions_Detail ON
tbl_Road_Restrictions.Road_Restriction_ID=tbl_Road_Restrictions_Detail.Road_
Restriction_ID;


The two tables are below (Linked by Road_Restriction_ID).
Can someone give me some idea(s) on how to achieve this?

The object doesn't contain the Automation object
'tbl_Road_Restrictions_Detail.

You tried to run a Visual Basic procedure to set a property for and object.
However, the component doesn't make the property or method available
for
Automation operations.
 
E

Evi

Sorry, got a bit lost with the combination of line wrapping in the email and
those long underscored table names. Ive just deleted the underscores in
Word, mended the lines and the whole thing is clearer now.
This threw me
'I want to be able to link a continuous form to another continous
form/subform.'

I think you may be trying to go from one subform to another subform, both
within a main form.
Your error message may be arising because one of your subforms hasn't
refreshed yet. You need to find the thing you were doing just before the
error message appears and put in the Requery code.
The sort of thing you may need in your 1st subform is

Private Sub Form_Current()

'activates as soon as you go to a new record

Me.Parent.YourSecondSubform.Requery

'replace YourSecondSubform with its real name

End Sub



You may even need to requery one of the subforms after you add a new record
to the main form.



Then the way to reference it is



Me.YourSubformsName.Requery










Me.Parent.




efandango said:
I have not used any visual basic code to sync the two forms.

I did state in my original post what two table were involved. How they were
linked. I had linked the two forms just like you suggested. I alsoo gave full
details of the table structures. I'm slightly confused by your reply stating
that none of these things were mentioned. Perhaps you didn't get the full
posting?

Evi said:
I guess Access is trying to protect us from the aesthetically ugly results
of putting a subform into a main form :)
You haven't given the visual basic you have used to 'sync the 2 forms' so I
can't comment on your error message.
One thing, you've only mentioned 1 record source for both forms, maybe this
was just to save space. The usual structure would be to have a main form
based on tblRoadRestriction (or on a query based on that table and the
subform based on tbl (or query) RoadRestrictionDetails. They would then by
linked by RoadRestrictionID
Evi
efandango said:
I want to be able to link a continuous form to another continous form/subform
(but not contained withing the master form). Access will not allow me
to
do
this, but I was wondering if there was a manual/pseudo way of doing this?

I have managed to link/synch the two forms, but when I try to create a new
record by using any of the fields on the 'sub form', I get this pop-up error
message:
The object doesn't contain the Automation object
'tbl_Road_Restrictions_Detail.

You tried to run a Visual Basic procedure to set a property for and object.
However, the component doesn't make the property or method available for
Automation operations.

But when I say OK to the error box, it still allows me to fill in the fields
and create the record. I want to fix this problem, but don't know how.
(I'
m
not even sure what the error means)
The two tables are below and are [Linked by Road_Restriction_ID]. Can
someone give me some idea(s) on how to resolve this?

Table Structures
tbl_Road_Restrictions
Road_Restriction_ID AutoNumber
Road_Name_From Text
Road_Name_To Text
Restriction Text
Run_No Number
Direction_From Text
Direction_To Text
Junction_ID Number

tbl_Road_Restrictions_Detail
Road_Restriction_Detail_ID AutoNumber
Road_Restriction_ID Number
Run_Direction Text
Run_waypoint Text
Postcode Text
Run_No Number



Form Structures

frm_Road_Restrictions
Link Master Fields: [Run_No]
LinkChild Fields: [Run_No]
Record Source: tbl_Road_Restrictions


frm_Road_Restrictions_Detail
Link Master Fields:
Forms![frm_Runs]![frm_Road_Restrictions].Form![Road_Restriction_ID]
LinkChild Fields: [Road_Restriction_ID]

Record Source:
SELECT tbl_Road_Restrictions_Detail.Road_Restriction_Detail_ID,
tbl_Road_Restrictions_Detail.Road_Restriction_ID,
tbl_Road_Restrictions_Detail.Run_Direction,
tbl_Road_Restrictions_Detail.Run_waypoint FROM tbl_Road_Restrictions INNER
JOIN tbl_Road_Restrictions_Detail ON
tbl_Road_Restrictions.Road_Restriction_ID=tbl_Road_Restrictions_Detail.Road_
Restriction_ID;
The two tables are below (Linked by Road_Restriction_ID).
Can someone give me some idea(s) on how to achieve this?

The object doesn't contain the Automation object
'tbl_Road_Restrictions_Detail.

You tried to run a Visual Basic procedure to set a property for and object.
However, the component doesn't make the property or method available for
Automation operations.
 
E

efandango

Evi, Bruce.

Thanks for your input. The problem was just a 'buggy situation' relating to
the first two fields which happend to be combo's that looked up the data. I
had them set to Autolookup from the table design stage. I have come accross
this problem in previous versions of access, where if you set the combo and
rowsource, etc while in table design; it somehow creates problems later on
when you select that field in forms design. I'm not sure why it gives these
problems, but ecist they do. I deleted the references in table design, and
just created them with the combo wizard on the form design, and all was well.
Seems like my various links were working all the time, but the buggy combo
sitation was obscuring this.

For the record, I was wrong when i said they were not linked to a master
form. I overlooked the fact that a tab page belongs to a master form. Which
was frm_Runs. The llinked to the first subform was Run_No and the link to the
2nd subform was Road_Restriction_ID. I did state these two links, but forget
to qualify the Run_No as belonginf to the master form.

sorry to mislead you on this. All is now working fine.



Evi said:
Sorry, got a bit lost with the combination of line wrapping in the email and
those long underscored table names. Ive just deleted the underscores in
Word, mended the lines and the whole thing is clearer now.
This threw me
'I want to be able to link a continuous form to another continous
form/subform.'

I think you may be trying to go from one subform to another subform, both
within a main form.
Your error message may be arising because one of your subforms hasn't
refreshed yet. You need to find the thing you were doing just before the
error message appears and put in the Requery code.
The sort of thing you may need in your 1st subform is

Private Sub Form_Current()

'activates as soon as you go to a new record

Me.Parent.YourSecondSubform.Requery

'replace YourSecondSubform with its real name

End Sub



You may even need to requery one of the subforms after you add a new record
to the main form.



Then the way to reference it is



Me.YourSubformsName.Requery










Me.Parent.




efandango said:
I have not used any visual basic code to sync the two forms.

I did state in my original post what two table were involved. How they were
linked. I had linked the two forms just like you suggested. I alsoo gave full
details of the table structures. I'm slightly confused by your reply stating
that none of these things were mentioned. Perhaps you didn't get the full
posting?

Evi said:
I guess Access is trying to protect us from the aesthetically ugly results
of putting a subform into a main form :)
You haven't given the visual basic you have used to 'sync the 2 forms' so I
can't comment on your error message.
One thing, you've only mentioned 1 record source for both forms, maybe this
was just to save space. The usual structure would be to have a main form
based on tblRoadRestriction (or on a query based on that table and the
subform based on tbl (or query) RoadRestrictionDetails. They would then by
linked by RoadRestrictionID
Evi
I want to be able to link a continuous form to another continous
form/subform
(but not contained withing the master form). Access will not allow me to
do
this, but I was wondering if there was a manual/pseudo way of doing this?

I have managed to link/synch the two forms, but when I try to create a new
record by using any of the fields on the 'sub form', I get this pop-up
error
message:
The object doesn't contain the Automation object
'tbl_Road_Restrictions_Detail.

You tried to run a Visual Basic procedure to set a property for and
object.
However, the component doesn't make the property or method available for
Automation operations.

But when I say OK to the error box, it still allows me to fill in the
fields
and create the record. I want to fix this problem, but don't know how. (I'
m
not even sure what the error means)
The two tables are below and are [Linked by Road_Restriction_ID]. Can
someone give me some idea(s) on how to resolve this?

Table Structures
tbl_Road_Restrictions
Road_Restriction_ID AutoNumber
Road_Name_From Text
Road_Name_To Text
Restriction Text
Run_No Number
Direction_From Text
Direction_To Text
Junction_ID Number

tbl_Road_Restrictions_Detail
Road_Restriction_Detail_ID AutoNumber
Road_Restriction_ID Number
Run_Direction Text
Run_waypoint Text
Postcode Text
Run_No Number



Form Structures

frm_Road_Restrictions
Link Master Fields: [Run_No]
LinkChild Fields: [Run_No]
Record Source: tbl_Road_Restrictions


frm_Road_Restrictions_Detail
Link Master Fields:
Forms![frm_Runs]![frm_Road_Restrictions].Form![Road_Restriction_ID]
LinkChild Fields: [Road_Restriction_ID]

Record Source:
SELECT tbl_Road_Restrictions_Detail.Road_Restriction_Detail_ID,
tbl_Road_Restrictions_Detail.Road_Restriction_ID,
tbl_Road_Restrictions_Detail.Run_Direction,
tbl_Road_Restrictions_Detail.Run_waypoint FROM tbl_Road_Restrictions INNER
JOIN tbl_Road_Restrictions_Detail ON

tbl_Road_Restrictions.Road_Restriction_ID=tbl_Road_Restrictions_Detail.Road_
Restriction_ID;


The two tables are below (Linked by Road_Restriction_ID).
Can someone give me some idea(s) on how to achieve this?

The object doesn't contain the Automation object
'tbl_Road_Restrictions_Detail.

You tried to run a Visual Basic procedure to set a property for and
object.
However, the component doesn't make the property or method available for
Automation operations.
 
E

Evi

One more nail in the coffin of those wicked Autolookups!
Thanks for alerting us. Someone is sure to suffer from the same problem at
some time.
Evi
efandango said:
Evi, Bruce.

Thanks for your input. The problem was just a 'buggy situation' relating to
the first two fields which happend to be combo's that looked up the data. I
had them set to Autolookup from the table design stage. I have come accross
this problem in previous versions of access, where if you set the combo and
rowsource, etc while in table design; it somehow creates problems later on
when you select that field in forms design. I'm not sure why it gives these
problems, but ecist they do. I deleted the references in table design, and
just created them with the combo wizard on the form design, and all was well.
Seems like my various links were working all the time, but the buggy combo
sitation was obscuring this.

For the record, I was wrong when i said they were not linked to a master
form. I overlooked the fact that a tab page belongs to a master form. Which
was frm_Runs. The llinked to the first subform was Run_No and the link to the
2nd subform was Road_Restriction_ID. I did state these two links, but forget
to qualify the Run_No as belonginf to the master form.

sorry to mislead you on this. All is now working fine.



Evi said:
Sorry, got a bit lost with the combination of line wrapping in the email and
those long underscored table names. Ive just deleted the underscores in
Word, mended the lines and the whole thing is clearer now.
This threw me
'I want to be able to link a continuous form to another continous
form/subform.'

I think you may be trying to go from one subform to another subform, both
within a main form.
Your error message may be arising because one of your subforms hasn't
refreshed yet. You need to find the thing you were doing just before the
error message appears and put in the Requery code.
The sort of thing you may need in your 1st subform is

Private Sub Form_Current()

'activates as soon as you go to a new record

Me.Parent.YourSecondSubform.Requery

'replace YourSecondSubform with its real name

End Sub



You may even need to requery one of the subforms after you add a new record
to the main form.



Then the way to reference it is



Me.YourSubformsName.Requery










Me.Parent.




efandango said:
I have not used any visual basic code to sync the two forms.

I did state in my original post what two table were involved. How they were
linked. I had linked the two forms just like you suggested. I alsoo
gave
full
details of the table structures. I'm slightly confused by your reply stating
that none of these things were mentioned. Perhaps you didn't get the full
posting?

:

I guess Access is trying to protect us from the aesthetically ugly results
of putting a subform into a main form :)
You haven't given the visual basic you have used to 'sync the 2
forms'
so I
can't comment on your error message.
One thing, you've only mentioned 1 record source for both forms,
maybe
this
was just to save space. The usual structure would be to have a main form
based on tblRoadRestriction (or on a query based on that table and the
subform based on tbl (or query) RoadRestrictionDetails. They would
then
by
linked by RoadRestrictionID
Evi
I want to be able to link a continuous form to another continous
form/subform
(but not contained withing the master form). Access will not allow
me
to
do
this, but I was wondering if there was a manual/pseudo way of
doing
this?
I have managed to link/synch the two forms, but when I try to
create a
new
record by using any of the fields on the 'sub form', I get this pop-up
error
message:
The object doesn't contain the Automation object
'tbl_Road_Restrictions_Detail.

You tried to run a Visual Basic procedure to set a property for and
object.
However, the component doesn't make the property or method
available
for
Automation operations.

But when I say OK to the error box, it still allows me to fill in the
fields
and create the record. I want to fix this problem, but don't know
how.
(I'
m
not even sure what the error means)
The two tables are below and are [Linked by Road_Restriction_ID]. Can
someone give me some idea(s) on how to resolve this?

Table Structures
tbl_Road_Restrictions
Road_Restriction_ID AutoNumber
Road_Name_From Text
Road_Name_To Text
Restriction Text
Run_No Number
Direction_From Text
Direction_To Text
Junction_ID Number

tbl_Road_Restrictions_Detail
Road_Restriction_Detail_ID AutoNumber
Road_Restriction_ID Number
Run_Direction Text
Run_waypoint Text
Postcode Text
Run_No Number



Form Structures

frm_Road_Restrictions
Link Master Fields: [Run_No]
LinkChild Fields: [Run_No]
Record Source: tbl_Road_Restrictions


frm_Road_Restrictions_Detail
Link Master Fields:
Forms![frm_Runs]![frm_Road_Restrictions].Form![Road_Restriction_ID]
LinkChild Fields: [Road_Restriction_ID]

Record Source:
SELECT tbl_Road_Restrictions_Detail.Road_Restriction_Detail_ID,
tbl_Road_Restrictions_Detail.Road_Restriction_ID,
tbl_Road_Restrictions_Detail.Run_Direction,
tbl_Road_Restrictions_Detail.Run_waypoint FROM
tbl_Road_Restrictions
INNER
JOIN tbl_Road_Restrictions_Detail ON
tbl_Road_Restrictions.Road_Restriction_ID=tbl_Road_Restrictions_Detail.Road_
Restriction_ID;


The two tables are below (Linked by Road_Restriction_ID).
Can someone give me some idea(s) on how to achieve this?

The object doesn't contain the Automation object
'tbl_Road_Restrictions_Detail.

You tried to run a Visual Basic procedure to set a property for and
object.
However, the component doesn't make the property or method
available
for
Automation operations.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top