It looks to me that a memo field that is different in the first bytes
(<255???) is detected, but one that is different past that limit is not.
Is this a true assumption?


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.675 / Virus Database: 437 - Release Date: 03/05/2004

Re: Memo Field Comparaison by Stefan

Stefan
Sat May 22 04:41:11 CDT 2004

"Erik Vandamme" <erik@tunwand.com.au> schrieb im Newsbeitrag
news:40aeb40a$0$9409$5a62ac22@freenews.iinet.net.au...
> It looks to me that a memo field that is different in the first bytes
> (<255???) is detected, but one that is different past that limit is not.
> Is this a true assumption?

I think not, the test.prg below seems to be able to get the difference.
Index expressions are limited to 240 bytes though...

hth
-Stefan

* memocomptest.prg
LOCAL cString, oError
cString = REPLICATE('x',300)
CREATE CURSOR temp (memo1 M, memo2 M)
CLEAR
INSERT INTO temp VALUES (m.cString, m.cString)
? memo1 == memo2 && equal
INSERT INTO temp VALUES (m.cString, m.cString + 'a')
? memo1 == memo2 && .F., not equal

TRY
INDEX ON memo2 TAG memo2
CATCH TO oError
? oError.ErrorNo, oError.Message
ENDTRY
SET COLLATE TO "MACHINE"
INDEX ON LEFT(memo2,240) TAG memo2
? SEEK(m.cString) && .F., not found
*