Trim won't work

[Me again]

Greetings

Many moons ago in an older version of Access I created a database to
administer various aspects of home life, including a facility to print
address labels for everyone who is marked as eligible for a Christmas card -
so that function only gets used once a year.

It worked last year when I was using Office 2000. During this year though I
have acquired Office 2002 (yes out of date still, but at least it's legal!).

When I just tried to print the labels a window opened up, headed Enter
Parameter Value - asking me to input a value for "Trim".

Trouble is it's so long since I created this or did any such work with
Access that I've forgotten most of the design stuff.

There is a macro that opens a Report, which shows a label design, and each
line in that starts =Trim(

for instance first line is =Trim([ccardname] & "" &[lastname])

second line is =Trim([line1])

and so on.

It never used to ask for a Parameter value, it just printed. Whatever I
input into this new window, I just get pages printed with the word "error"

Did something change between 2000 and 2002, or any other ideas?

The rest of the database is working fine.

 

[Ken Snell [MVP]]

If any of the database's references are messed up -- you can get that
prompt.

Try following these steps (from a post by Douglas Steele, MVP):

This can be caused by differences in either the location or file version of
certain files between the machine where the application was developed, and
where it's being run (or the file missing completely from the target
machine). Such differences are common when new software is installed.

On the machine(s) where it's not working, open any code module (or open the
Debug Window, using Ctrl-G, provided you haven't selected the "keep debug
window on top" option). 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)

For far more than you could ever want to know about this problem, check out
http://members.rogers.com/douglas.j.steele/AccessReferenceErrors.html

--

Ken Snell
<MS ACCESS MVP>

Greetings

Many moons ago in an older version of Access I created a database to
administer various aspects of home life, including a facility to print
address labels for everyone who is marked as eligible for a Christmas card -
so that function only gets used once a year.

It worked last year when I was using Office 2000. During this year though I
have acquired Office 2002 (yes out of date still, but at least it's legal!).

When I just tried to print the labels a window opened up, headed Enter
Parameter Value - asking me to input a value for "Trim".

Trouble is it's so long since I created this or did any such work with
Access that I've forgotten most of the design stuff.

There is a macro that opens a Report, which shows a label design, and each
line in that starts =Trim(

for instance first line is =Trim([ccardname] & "" &[lastname])

second line is =Trim([line1])

and so on.

It never used to ask for a Parameter value, it just printed. Whatever I
input into this new window, I just get pages printed with the word "error"

Did something change between 2000 and 2002, or any other ideas?

The rest of the database is working fine.

 

[Jeff Conrad]

Hi,

".....everyone who is marked as eligible for a Christmas card...."

Humm...sort of a "Naughty" or "Nice" kind of thing huh?
;-)

Anyway, back to the 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://members.rogers.com/douglas.j.steele/AccessReferenceErrors.html

http://members.iinet.net.au/~allenbrowne/ser-38.html

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

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

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

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

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

--
Jeff Conrad
Access Junkie
Bend, Oregon

Greetings

Many moons ago in an older version of Access I created a database to
administer various aspects of home life, including a facility to print
address labels for everyone who is marked as eligible for a Christmas card -
so that function only gets used once a year.

It worked last year when I was using Office 2000. During this year though I
have acquired Office 2002 (yes out of date still, but at least it's legal!).

When I just tried to print the labels a window opened up, headed Enter
Parameter Value - asking me to input a value for "Trim".

Trouble is it's so long since I created this or did any such work with
Access that I've forgotten most of the design stuff.

There is a macro that opens a Report, which shows a label design, and each
line in that starts =Trim(

for instance first line is =Trim([ccardname] & "" &[lastname])

second line is =Trim([line1])

and so on.

It never used to ask for a Parameter value, it just printed. Whatever I
input into this new window, I just get pages printed with the word "error"

Did something change between 2000 and 2002, or any other ideas?

The rest of the database is working fine.

 

[Me again]

Guys - if either of you need references for knighthood, just let me know.
Worked a treat!

Can't thank you enough.

 

[Jeff Conrad]

You're welcome, glad we could help.
Hummm....Sir Snell and Sir Conrad.
Nice!

 

[Ken Snell [MVP]]

You're welcome, glad we could help.
Hummm....Sir Snell and Sir Conrad.
Nice!

< chuckling grin ! >

 

[Lynn Trapp]

Hummm....Sir Snell and Sir Conrad.

Knights of the Order of St. Access, with special commendation for
non-spreadsheet development.

;-)