CurrentDB.OpenRecordset

  • Thread starter Thread starter MPM1100
  • Start date Start date
M

MPM1100

Hi all,

I'm reverting back to Access 97 and running into a problem with the app and
the use of CurrentDB.OpenRecordset.

I am submitting a SQL statement for the domain which is where the problem
exists. In the SQL statment I am using the function Nz() which works fine
when viewing a queries in the query window. However, when I try to submit
the same SQL to OpenRecordset, I get an error telling me that the function
'Nz' is undefined.

It's been a while since I worked with A97, but I don't recall ever having
such problems. Is there a reference or otherwise I might be missing here?

Thanks in advance...
MPM
 
The first thing I'd suggest is that you check the references. Open any VBA
module and select Tools | References from the menu bar. Are any of the
selected references (they'll all be at the top of the list) have MISSING: in
front of them? If so, uncheck them and back out of the dialog. Select
Compile All Modules under the Debug menu. If the application compiles
cleanly, you didn't need the reference(s). If it doesn't, go back into the
dialog and reselect whatever you unselected.

If none have "MISSING:", select an additional reference at random, back out
of the dialog, then go back in and unselect the reference you just added. If
that doesn't solve the problem, try to unselect as many of the selected
references as you can (Access may not let you unselect them all), back out
of the dialog, then go back in and reselect the references you just
unselected. (NOTE: write down what the references are before you delete
them, because they'll be in a different order when you go back in)
 
Thanks for the input...

Figured this one out... It was a case sensitivity problem that 2000 and later
ignore. Hope this is helpful to anyone else...

Best!
 
I'm curious as to what exactly you found was case sensitive.

In general, Access isn't case sensitive.
 
Back
Top