Alaska Software Inc. - alltrim() bug
Username: Password:
AuthorTopic: alltrim() bug
Joe Carrick alltrim() bug
on Mon, 21 Apr 2008 12:51:36 -0700
In some cases - not sure exactly what determining factors are - alltrim 
fails to give correct answer.  But anyway, here's one that worked and 
then didn't.

***********************************************************************
?? Vendors->BuyClass -> " XX"
set filter to alltrim(Vendors->BuyClass) <> "XX"

resulted in those records with " XX" as that field being visible.

***********************************************************************
?? Vendors->BuyClass -> " XX"
replace Vendors->BuyClass with " XX"
set filter to alltrim(Vendors->BuyClass) <> "XX"

resulted in those records with " XX" as that field being invisible.

***********************************************************************
?? Vendors->BuyClass -> " XX"
set filter to right(rtrim(Vendors->BuyClass),2) <> "XX"

resulted in those records with " XX" as that field being invisible.

***********************************************************************

What could cause the first case to give the incorrect result ?
Hubert Brandel Re: alltrim() bug
on Tue, 22 Apr 2008 00:06:42 +0200
Joe Carrick schrieb:

> What could cause the first case to give the incorrect result ?

alltrim() will remove blanks, but there is another byte with 'nothing to 
see'. CHR(255) or fixed blanks could be there. If you have such a 
problem, check witch ASCII() code is in there.

In Memofields there could be a  chr(13)+chr(10) for new line behind some 
  blanks or a chr(9) (TAB).


----------------

Ich empfehle:  www.xbaseforum.de  (in deutsch)

Homepage:

German  - www.familie-brandel.de/index.htm
English - www.familie-brandel.de/index_e.htm