Trim and Ucase

[Bill]

Just set up a system for a lady in my office and her
Access 2002 is not recognizing the trim or Ucase commands
(even when the wizard puts them into the report). It's a
multi-license deal so her Access is the same as mine, but
databases that do fine on my system run into this problem
on hers. Anybody seen this problem before? ... any
suggestions?

 

[Douglas J. Steele]

Sounds like a References problem. In essence, there's a difference between
certain shared files between the machine where the application was developed
and the machine where it's going to be run. Such problems can be caused by
installing (or removing) other software from a workstation.

On the machine(s) where it's not working, open any code module, then select
Tools | References from the menu bar. Examine all of the selected
references.

If any of the selected references have "MISSING:" in front of them, unselect
them, and back out of the dialog.
If you really need the reference(s) you just unselected (you can tell by
doing a Compile All Modules), go back in and reselect them.

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)

 

[Guest]

There aren't any code modules in the database in question
and I don't appear to have a References option under
tools? I did notice a conversion error on one of the
databases listing a missing or broken VBE reference to
the file dao2535 .... any idea how to locate that?

 

[Peter De Baets]

There may be a problem with her library references. Open any module in
design mode and click Tools > References. Are any checked libraries in
the list "MISSING:"? If so, you must resolve these before continuing.
Either remove or fix (click browse and find the library) the missing
references. If the missing references can't be resolved, an Access
re-install may help.

Hope this helps,

Peter De Baets
Peter's Software - MS Access Tools for Developers
http://www.peterssoftware.com

 

[Douglas J. Steele]

If you don't have any existing modules, either create one (you don't even
have to save it once you're done), or simply open the Debug window using
Ctrl-G and follow the instructions I gave.

You definitely shouldn't have a reference to dao2535.dll in an Access 2002
database. That was used by Access 97 to ensure compatibility when converting
from Access 2.0. I don't believe it's worked with any version of Access
since then.