Problem after migrating from A2K to A2003

[Guest]

Hi Guys,

I developed an application years ago in A2K. Recently when I migrated it to
A2003 I found I get an #NAME problem with the following code which is the
record source for a textbox. Any help will be greatly appreciated.

=[Forms]![frmNewDeals].Recordset.AbsolutePosition+1

 

[crawford.francis]

Gary,

Trry Form_frmNewDeals_1.Recordset.AbsolutePosition+1
Reference to a form changed just a bit....

 

[Marshall Barton]

I developed an application years ago in A2K. Recently when I migrated it to
A2003 I found I get an #NAME problem with the following code which is the
record source for a textbox. Any help will be greatly appreciated.

=[Forms]![frmNewDeals].Recordset.AbsolutePosition+1

I think you could get that error if frmNewDeals is not open.

 

[Guest]

--
Gary in Michigan, USA
That doesn't seem to do it, still returns #Name. This textbox is a record
counter on frmNewDeals. When I copy it and run it on my A2K machine it works
fine. Thanks!

 

[Guest]

Hi Marsh,

The textbox is on frmNewDeals, so it is definitely open. The code works
fine if I copy it back to my A2K machine. Any other thoughts?

Thanks!


--
Gary in Michigan, USA

I developed an application years ago in A2K. Recently when I migrated it to
A2003 I found I get an #NAME problem with the following code which is the
record source for a textbox. Any help will be greatly appreciated.

=[Forms]![frmNewDeals].Recordset.AbsolutePosition+1

I think you could get that error if frmNewDeals is not open.

 

[Marshall Barton]

The textbox is on frmNewDeals, so it is definitely open. The code works
fine if I copy it back to my A2K machine. Any other thoughts?

Odd. Such a simple expression doesn't provide many
opportunities for that error. I tried the same thing in A03
and it worked as expected.

Only one other stray thought. You may not have the same
references in the A03 as you did in A2K. It's worth
checking, especially the ADO and DAO references. Or maybe
you have the right libraries but are referenceing the wrong
version?? This may be useful if you are not sure about some
aspects of references problems:
http://www.accessmvp.com/djsteele/AccessReferenceErrors.html

 

[Guest]

Umm, no dice there. References are the same on the two machines, except that
the A2003 machine has Microsoft Acess 11.0 Object Library instead of 9.0 like
the A2K machine. I've tried creating a new blank database and then importing
all the objects, compacting, converting to A2003, and I've tried making a
complete new test form from scratch and attaching it to the table in question
so that it would "see" the same records, and then used the code as a control
source and I still get the same #Name problem. I get this on both the A2003
machines I have. Thanks anyway for trying.

 

[Marshall Barton]

Umm, no dice there. References are the same on the two machines, except that
the A2003 machine has Microsoft Acess 11.0 Object Library instead of 9.0 like
the A2K machine. I've tried creating a new blank database and then importing
all the objects, compacting, converting to A2003, and I've tried making a
complete new test form from scratch and attaching it to the table in question
so that it would "see" the same records, and then used the code as a control
source and I still get the same #Name problem. I get this on both the A2003
machines I have. Thanks anyway for trying.

Sorry I couldn't be more help, but it's tough when I can't
reproduce the problem.