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

AXP: Err 2467 and Recordsource change - BUG???

P: n/a
Hi Folks!

I have this strange error that happens after conversion from A97 to
AXP (2000-Format). Looks like a bug to me - I've lost 3 days with no
result.

I use a form with 2 subforms on it, one to set criterias and one that
reflects data upon selected criterias. This works perfectly. But
sometimes I need to get started with an already "restricted" dataset.
So what I do is to change at run-time the form.subform.recordset
property from qmyQuery to something like SELECT * FROM qmyQuery WHERE
fld = ...

This is done in the Form_Load Event of the parent form through a call
to a generic procedure (Me as argument). As soon as it get's back the
Me object is invalid. I tracked the problem down to the line of code
where value Datasource of subform is changed.

This worked perfectly in A97.

Please help, I need to switch to AXP soon.

Thank you very much.
Gianluca L. Monteleone
Nov 12 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
Remote debugging is difficult, at best. It isn't "at best" when only a
description of the general environment and a general description of the
problem are provided. That is, there's no guarantee that someone here will
be able to solve your problem if you provide a concise, but precise
description with necessary detail -- but it is unlikely that anyone CAN with
no more information than this.

Please clarify so someone will have a chance at helping. Show the code. Show
the specific line where the error occurs. Show the specific error, number
and description, if applicable.

Larry Linson
Microsoft Access MVP

"Gianluca L. Monteleone" <gl**@gmx.net> wrote in message
news:55**************************@posting.google.c om...
Hi Folks!

I have this strange error that happens after conversion from A97 to
AXP (2000-Format). Looks like a bug to me - I've lost 3 days with no
result.

I use a form with 2 subforms on it, one to set criterias and one that
reflects data upon selected criterias. This works perfectly. But
sometimes I need to get started with an already "restricted" dataset.
So what I do is to change at run-time the form.subform.recordset
property from qmyQuery to something like SELECT * FROM qmyQuery WHERE
fld = ...

This is done in the Form_Load Event of the parent form through a call
to a generic procedure (Me as argument). As soon as it get's back the
Me object is invalid. I tracked the problem down to the line of code
where value Datasource of subform is changed.

This worked perfectly in A97.

Please help, I need to switch to AXP soon.

Thank you very much.
Gianluca L. Monteleone

Nov 12 '05 #2

P: n/a
I suspect you haven't been fully accurate in your terminology here.

You write:
So what I do is to change at run-time the form.subform.recordset
property from qmyQuery to something like SELECT * FROM qmyQuery WHERE
fld = ... In Access 97, forms did not expose a property named Recordset, so it's
unlikely that any code changing that property would have run.

Later, you write:I tracked the problem down to the line of code
where value Datasource of subform is changed. Again, Datasource is not an exposed property of forms in any version of
Access I know of.

Perhaps if you posted some actual code...

- Turtle
"Gianluca L. Monteleone" <gl**@gmx.net> wrote in message
news:55**************************@posting.google.c om... Hi Folks!

I have this strange error that happens after conversion from A97 to
AXP (2000-Format). Looks like a bug to me - I've lost 3 days with no
result.

I use a form with 2 subforms on it, one to set criterias and one that
reflects data upon selected criterias. This works perfectly. But
sometimes I need to get started with an already "restricted" dataset.
So what I do is to change at run-time the form.subform.recordset
property from qmyQuery to something like SELECT * FROM qmyQuery WHERE
fld = ...

This is done in the Form_Load Event of the parent form through a call
to a generic procedure (Me as argument). As soon as it get's back the
Me object is invalid. I tracked the problem down to the line of code
where value Datasource of subform is changed.

This worked perfectly in A97.

Please help, I need to switch to AXP soon.

Thank you very much.
Gianluca L. Monteleone

Nov 12 '05 #3

P: n/a
Sorry, what I meant was MyForm.MySubForm.Form.RecordSource=...
Anyway, I found a workaround by setting RecordSource to a dummy value
and then setting it to the actual SQL string. It work's this way, but
still seems to me as if there's a bug in DAO 3.6/AXP.
Thank you for your reply.
-- Gianluca L. Monteleone
Nov 12 '05 #4

P: n/a
I had this same issue. Found that my issue was using the instr()
function in the source query. It worked on my win2000/accessXP but
instr() does not work on the Win98/access2000. In essence what s
happening is that the subform is failing to load and therefor can't be
seen from the main forms VBA code. Verify that your subform can open.

Adolph
gl**@gmx.net (Gianluca L. Monteleone) wrote in message news:<55**************************@posting.google. com>...
Hi Folks!

I have this strange error that happens after conversion from A97 to
AXP (2000-Format). Looks like a bug to me - I've lost 3 days with no
result.

I use a form with 2 subforms on it, one to set criterias and one that
reflects data upon selected criterias. This works perfectly. But
sometimes I need to get started with an already "restricted" dataset.
So what I do is to change at run-time the form.subform.recordset
property from qmyQuery to something like SELECT * FROM qmyQuery WHERE
fld = ...

This is done in the Form_Load Event of the parent form through a call
to a generic procedure (Me as argument). As soon as it get's back the
Me object is invalid. I tracked the problem down to the line of code
where value Datasource of subform is changed.

This worked perfectly in A97.

Please help, I need to switch to AXP soon.

Thank you very much.
Gianluca L. Monteleone

Nov 12 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.