dbTalk Databases Forums  

RTrim returns #error

comp.database.ms-access comp.database.ms-access


Discuss RTrim returns #error in the comp.database.ms-access forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Mark Roach
 
Posts: n/a

Default RTrim returns #error - 09-02-2003 , 06:42 PM






I have a strange issue, I have a number of tables linked to an informix
database. The queries have been working just fine for quite a while, but
suddenly, all queries that use RTrim (or LTrim or Trim for that matter)
return #ERROR for whichever field is using RTrim.

Even stranger, is that if I create a new database and link the same
tables, it works just fine. This is a simple case that shows the error

SELECT xcal_patdemo.patid, RTrim([xcal_patdemo]![lname]) AS Expr1
FROM xcal_patdemo
WHERE (((xcal_patdemo.patid)="108264"));

Works just fine in my test database, but not in my real one.
If I leave out RTrim, it works (but is padded, of course).

It seems like RTrim is somehow "missing" or been overridden somehow.

Any suggestions?

Thanks,

Mark

Reply With Quote
  #2  
Old   
tom
 
Posts: n/a

Default Re: RTrim returns #error - 09-05-2003 , 12:05 AM






Mark,

Generally, this means that one of your references has gone bad. did
you move the db from one PC to another? if the new PC does not have
exactly the same .dlls, it may not be able to find the new ones.
usually, it will find newer versions, but i don't think it will ever
find older versions. upgrading other software or applying MS patches
can also cause this. (Welcome to DLL Hell. anyone looking forward to
having VB.NET in Access?)

in the VBE (Alt + F11 from the db container) select Tools menu, then
References. chances are you will find MISSING next to one of the
first few items in the list. find one with a very similar name and
check it. exit the references pop-up and everthing should be fine.

Good luck. tom

Mark Roach <mrroach (AT) okmaybe (DOT) com> wrote

Quote:
I have a strange issue, I have a number of tables linked to an informix
database. The queries have been working just fine for quite a while, but
suddenly, all queries that use RTrim (or LTrim or Trim for that matter)
return #ERROR for whichever field is using RTrim.

Even stranger, is that if I create a new database and link the same
tables, it works just fine. This is a simple case that shows the error

SELECT xcal_patdemo.patid, RTrim([xcal_patdemo]![lname]) AS Expr1
FROM xcal_patdemo
WHERE (((xcal_patdemo.patid)="108264"));

Works just fine in my test database, but not in my real one.
If I leave out RTrim, it works (but is padded, of course).

It seems like RTrim is somehow "missing" or been overridden somehow.

Any suggestions?

Thanks,

Mark

Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.