By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
455,656 Members | 1,727 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 455,656 IT Pros & Developers. It's quick & easy.

Subform errors - can you check this...

P: n/a
I wonder if anyone would have 5 minutes to check this for me. Access XP
with new database created:

Simple table tblTest: ID=autonumber, F1=Text with a few sample records
frmSub has this as its recordsource and is set to datasheet view
frmMain is unbound and has a subform control named 'sbfSub1' with 'frmSub'
as the source object which is placed in the form footer. It has a button on
the detail section with the following code:
MsgBox Me.sbfSub1.Form.RecordSource

This works fine if the form footer section is visible, but if not I get
error 2455: Invalid reference to property. I can make the subform control
invisible and the error does not occur, but I thought I would be able to
make the footer invisible. Is this a known thing, or am I doing something
silly?
Feb 16 '06 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Just checked, same with Access 2003 here.

Possible workaround:
Make the footer.height *very small*, make the sub.height even smaller...
0,011 cm for the sub and 0,019 cm for the footer works here, which is in fact invisible (to me ...)
But I have NO Clue whatever about what you are trying to accomplish here...

Arno R

"Anthony England" <ae******@oops.co.uk> schreef in bericht news:dt**********@nwrdmz02.dmz.ncs.ea.ibs-infra.bt.com...
I wonder if anyone would have 5 minutes to check this for me. Access XP
with new database created:

Simple table tblTest: ID=autonumber, F1=Text with a few sample records
frmSub has this as its recordsource and is set to datasheet view
frmMain is unbound and has a subform control named 'sbfSub1' with 'frmSub'
as the source object which is placed in the form footer. It has a button on
the detail section with the following code:
MsgBox Me.sbfSub1.Form.RecordSource

This works fine if the form footer section is visible, but if not I get
error 2455: Invalid reference to property. I can make the subform control
invisible and the error does not occur, but I thought I would be able to
make the footer invisible. Is this a known thing, or am I doing something
silly?

Feb 16 '06 #2

P: n/a
"Arno R" <ar***********@tiscali.nl> wrote in message
news:43**********************@text.nova.planet.nl. ..
Just checked, same with Access 2003 here.

Possible workaround:
Make the footer.height *very small*, make the sub.height even smaller...
0,011 cm for the sub and 0,019 cm for the footer works here, which is in
fact invisible (to me ...)
But I have NO Clue whatever about what you are trying to accomplish here...

Arno R

"Anthony England" <ae******@oops.co.uk> schreef in bericht
news:dt**********@nwrdmz02.dmz.ncs.ea.ibs-infra.bt.com...
I wonder if anyone would have 5 minutes to check this for me. Access XP
with new database created:

Simple table tblTest: ID=autonumber, F1=Text with a few sample records
frmSub has this as its recordsource and is set to datasheet view
frmMain is unbound and has a subform control named 'sbfSub1' with 'frmSub'
as the source object which is placed in the form footer. It has a button
on
the detail section with the following code:
MsgBox Me.sbfSub1.Form.RecordSource

This works fine if the form footer section is visible, but if not I get
error 2455: Invalid reference to property. I can make the subform control
invisible and the error does not occur, but I thought I would be able to
make the footer invisible. Is this a known thing, or am I doing something
silly?



Thank you for checking. I wonder if this is a bug or whether it is supposed
to be like this. It seems strange that you can have the subform control set
to a tiny size and make it invisible, but if you set the footer to
invisible, you get this error.

By the way, I am not doing anything too strange. I am doing some stuff
which needs a number of user settings to be available for read/write access
and I use the subform's recordsource to do this. Normally, there is no need
to see the value of the settings so the idea was to place the subform on an
invisible footer. If I can't do it like this, then I will simply alter the
size of the form and, as it cannot be re-sized by the user anyway, they will
never see the bit at the bottom of the form.

If anyone has an explanation for this behaviour, please feel free...
Feb 16 '06 #3

This discussion thread is closed

Replies have been disabled for this discussion.