access97 to 2002 problems

  • Thread starter Thread starter alan
  • Start date Start date
A

alan

I just converted from 97 to office xp pro and have an
access file that the query has a mid$ statement in it.

The query now gives me a compile error. mid$ is still
legal in the help screen.

I even deleted the field and rebuilt the expression and it
still says compile error when i try to look at the data.

???
 
Alan-

Open any module in Design view. Choose References from the Tools menu.
Delete any libraries marked "missing." When you convert a database, you
sometimes get "legacy" libraries carried forward that don't exist. When you
have missing references in VB, all sorts of wierd stuff happens when you try
to use built-in functions anywhere.

Just curious, but why did you decide to convert the old 97 application?

--
John Viescas, author
"Microsoft Office Access 2003 Inside Out" (coming soon)
"Running Microsoft Access 2000"
"SQL Queries for Mere Mortals"
http://www.viescas.com/
(Microsoft Access MVP since 1993)
 
We moved the mdb to a new system that had the new version
of office. When I opened it it asked me to convert it.

I do not use any modules or macros, just many tables and
queries....

I looked at module references and there are only about 6
checked off. They all have a valid location.
There are hundreds listed that are not checked off.

I did not load office on this box. Is it possible to load
access without the functions portion? If so I guess I
could try to reload it.

Thanks
Alan
 
Six libraries sounds like a lot. You need Visual Basic for Applications,
Microsoft Access Object Library, and probably Microsoft DAO 3.x Object
library. It's possible that the conversion process did not include that
last library -- if you have code that opens recordsets, your project won't
compile. You might also have or need the Microsoft Office Object Library
and Microsoft ActiveX Data Objects 2.x Library.

I'm suspecting that some of your code won't compile after you converted.
Open any module again in Design view and choose Compile from the Debug menu.
If there are errors in the converted code, that can sometimes keep queries
from recognizing some of the built-in functions.

--
John Viescas, author
"Microsoft Office Access 2003 Inside Out" (coming soon)
"Running Microsoft Access 2000"
"SQL Queries for Mere Mortals"
http://www.viescas.com/
(Microsoft Access MVP since 1993)
 
Back
Top