Trim in label reports

[Guest]

Hell
I am using Access XP. When creating then running a label report, the Enter Parameter Value message box appears with the prompt Trim. Clicking OK displays the labels with #Error in place of the data. In Design View the following is entered for example =Trim([First Name] & " " & [Last Name]

By deleting Trim and the brackets, the data is correctly displayed in the label

However, Trim is useful so deleting it is not the answer. I am puzzled that the Enter Parameter Value message appears.

The database was converted from Access 97. The problem does not appear when using a database created using Access XP. Is this perhaps a compatibility issue?

Any suggestions for resolving this please

 

[Allen Browne]

Your database has a problem with references.

Press Ctrl+G to open the Immediate window.
Choose References from the Tools menu.
Look for any checked reference marked "MISSING".

More information:
http://allenbrowne.com/ser-38.html

--
Allen Browne - Microsoft MVP. Perth, Western Australia.

Reply to group, rather than allenbrowne at mvps dot org.

I am using Access XP. When creating then running a label report, the

Enter Parameter Value message box appears with the prompt Trim. Clicking OK
displays the labels with #Error in place of the data. In Design View the
following is entered for example =Trim([First Name] & " " & [Last Name])

By deleting Trim and the brackets, the data is correctly displayed in the label.

However, Trim is useful so deleting it is not the answer. I am puzzled

that the Enter Parameter Value message appears.

The database was converted from Access 97. The problem does not appear

when using a database created using Access XP. Is this perhaps a
compatibility issue?

 

[Denny W. Jones]

I had a similar problem and thought it might be helpful to share the
solution so others can learn...

My application was developed and expected to be installed on Windows 2000
with the Access Runtime. The client wanted to use it on XP and kept getting
the "TRIM()" errors mentioned in the original thread. As it turned out, the
problem was with a missing DAO350.dll file. XP doesn't
use this version. It uses DAO360.dll. To remedy it, I installed the 350
version on the XP machine and registered it.

To get to this point I opened the original non-MDE file, opened a code
window and looked at the references (CTRL-G). This showed me all of the
references that the database was expecting. I then looked on the XP machine
to determine which files were missing.

Thanks go to Allen for the direction he set me on to get to this solution.

Hope this helps someone.

Denny