Ucase([LastName]) is not acepted anymore

  • Thread starter Thread starter Brigham Siton
  • Start date Start date
B

Brigham Siton

Hello all. Using Access 97, I have a sub-procedure on our LastName control
that on LostFocus, it changes the last name to upper case.

Function that I am using is: Ucase([LastName])

This has been working after we applied some patches for Windows and some
patches for the Office. I am not sure which patch did it but the database
is residing on a Windows 2000 Advanced Server machine.

Any thoughts or solutions? Any other function I can use to make the
lastname change to all caps on lost focus?

Thank you very much for your help.
 
Brigham Siton said:
Hello all. Using Access 97, I have a sub-procedure on our LastName
control that on LostFocus, it changes the last name to upper case.

Function that I am using is: Ucase([LastName])

This has been working after we applied some patches for Windows and
some patches for the Office. I am not sure which patch did it but
the database is residing on a Windows 2000 Advanced Server machine.

Any thoughts or solutions? Any other function I can use to make the
lastname change to all caps on lost focus?

Thank you very much for your help.
Click to expand...

I'm not sure how your patches might have caused this, but it sounds very
much like a broken reference. So try the steps outline on Doug Steele's
page,


http://members.rogers.com/douglas.j.steele/AccessReferenceErrors.html
 
Brigham Siton said:
Hello all. Using Access 97, I have a sub-procedure on our LastName control
that on LostFocus, it changes the last name to upper case.

Function that I am using is: Ucase([LastName])

This has been working after we applied some patches for Windows and some
patches for the Office. I am not sure which patch did it but the database
is residing on a Windows 2000 Advanced Server machine.

Any thoughts or solutions? Any other function I can use to make the
lastname change to all caps on lost focus?
Click to expand...

You might have a references problem. Go to a code module and then Tools -
References and see if any of the checked ones are marked "Missing". This
will cause many built in functions to fail. You might be able to just
remove the reference if any are marked missing. Otherwise you need to
reinstall or re-register that library. Sometimes unchecking a library and
then going right back in an re-checking it will cure the problem.

BTW, wouldn't it be better to use AfterUpdate instead of LostFocus? With
LostFocus you are updating the field even if the user has done nothing
other than navigate to the control without changing it.
 
This has been working after we applied some patches for Windows and some
patches for the Office. I am not sure which patch did it but the database
is residing on a Windows 2000 Advanced Server machine.

Any thoughts or solutions?
Click to expand...

This appears to be the very common References bug. Open any
module in design view, or open the VBA editor by typing
Ctrl-G. Select Tools... References from the menu. One of the
..DLL files required by Access will probably be marked
MISSING. Uncheck it, recheck it, close and open Access.

If none are MISSING, check any reference; close and open
Access; then uncheck it again. This will force Access to
relink the libraries.
 
Back
Top