TRIM not working in Access2003

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hello Everyone, I am opening and modifying an MDB made with Access2000 in
Access2003.
I noticed that the TRIM function is giving trouble, because it seems to be
not accepted as it used to be in older versions of Access.
In detail: I have a query that extracts various anagraphic data from a
table, when preparing the report using the =Trim([whatever] & " " &
[whatever2]) line it start asking me a variable for the TRIM command and
then fills the field with the Trim command with an "#error" message.
I am on WinXP sp2 and Office2003 Sp2
I can add screengrabs of the problem if requested.
Thanks a lot in advance

Pier
~~~~~~~~~~~~~~~~~~~~
"Credo Quia Absurdum"
 
AlienXS said:
Hello Everyone, I am opening and modifying an MDB made with Access2000 in
Access2003.
I noticed that the TRIM function is giving trouble, because it seems to be
not accepted as it used to be in older versions of Access.
In detail: I have a query that extracts various anagraphic data from a
table, when preparing the report using the =Trim([whatever] & " " &
[whatever2]) line it start asking me a variable for the TRIM command and
then fills the field with the Trim command with an "#error" message.
I am on WinXP sp2 and Office2003 Sp2
I can add screengrabs of the problem if requested.
Thanks a lot in advance
Click to expand...

What's the name of the field? If it's whatever or whatever2, you'll get
that problem.
In any case, Trim works OK here. Send me your screenshots if you'd like.
I'll see if
I can get anything from them.

Tom Lake
 
?Any chance your .MDB has a MISSING reference? Open a code module, click
Tools | Reference, and see if any of the checked references are prefixed
with "MISSING".
 
Indeed, Thanks Jeff.
I still cannot understand why a barcode reference could interrupt what
should be a "native" command in Access... but I noticed that that was the
only reference missing and once installed the ocx (even if that report didnt
have any barcode at all) made the "Trim" work as expected... bah..
Thanks again :)
Pier
 
AlienXS said:
Indeed, Thanks Jeff.
I still cannot understand why a barcode reference could interrupt what
should be a "native" command in Access... but I noticed that that was
the only reference missing and once installed the ocx (even if that
report didnt have any barcode at all) made the "Trim" work as
expected... bah..
Click to expand...

ANY broken reference causes the symptoms you describe. The functions that
crap out need not have anything to do with the reference that is broken..
 
Back
Top