Trim won't work

[Rover]

I have a .mdb that works for all clients on a network except one. When
I run a report that has a TRIM function in it is run, the report comes
up with a box asking for a value of TRIM. On that machine, I notice
that under "References" in VBA it says "MISSING: Microsoft ActiveX
Objects 2.7 Library"

1) Might that be the problem?
2) how do I fix it?

TIA

Jim

 

[John Vinson]

I have a .mdb that works for all clients on a network except one. When
I run a report that has a TRIM function in it is run, the report comes
up with a box asking for a value of TRIM. On that machine, I notice
that under "References" in VBA it says "MISSING: Microsoft ActiveX
Objects 2.7 Library"

1) Might that be the problem?
Yep.

2) how do I fix it?

Uncheck it, unless you're in fact using ActiveX Data Objects in your
code. Or, uncheck it; close and open Access; and check it again, close
and open once more and see if that relinks it.

John W. Vinson[MVP]

 

[Jeff Conrad]

in message:

I have a .mdb that works for all clients on a network except one. When
I run a report that has a TRIM function in it is run, the report comes
up with a box asking for a value of TRIM. On that machine, I notice
that under "References" in VBA it says "MISSING: Microsoft ActiveX
Objects 2.7 Library"

1) Might that be the problem?
2) how do I fix it?

Here is my standard response on the References problem:

It is a References problem. The arch-nemesis of Access is missing references.

To fix the References problem follow these steps:
- Open any module in Design view.
- On the Tools menu, click References.
- At least one Reference should say "Missing". WRITE down the one(s) missing.
- Click to clear the check box for the type library or object library marked as "Missing:."
- Close the References Window box.
- Open the References Window back up. Hopefully, nothing should say Missing this time.
- Now go find that library/project(s) in the list that was missing.
- If more than one were missing, find the others and check them as well.
- Close the References box again.
- Now re-compile again. Debug--Compile.
- Hopefully you should not see any more compile errors.

If you'd like to read more about References, here's more info than you could possibly ever want to
know:

http://www.accessmvp.com/djsteele/AccessReferenceErrors.html

http://allenbrowne.com.au/ser-38.html

http://www.trigeminal.com/usenet/usenet026.asp

http://www.papwalker.com/dllhell/index-page2.html

http://www.access.qbuilt.com/html/gem_tips1.html#DAOLibRef

References that you must set when you use Microsoft Office Access 2003:
http://support.microsoft.com/?id=825796

ACC2002: References That You Must Set When You Work with Microsoft Access:
http://support.microsoft.com/?id=283115

ACC2000: How Access 2000 Resolves Visual Basic for Applications References
http://support.microsoft.com/?id=248941

ACC2000: How to Resolve Reference Issues in an Access Database
http://support.microsoft.com/?id=310803

List of the references that you must set when you work with Access 2000 or Access 97 database:
http://support.microsoft.com/?id=197110

ACC97: References That You Must Set When You Work with Microsoft Access
http://support.microsoft.com/?id=175484

ACC: VBA Functions Break in Database with Missing References
http://support.microsoft.com/?id=160870

 

[Immanuel Sibero]

Excellent references for references problems


Immanuel Sibero

 

[Jeff Conrad]

in message:

Excellent references for references problems

;-)