VFP9 error with ALLTRIM() in index "data type mismatch" 1

[RafiAli]

Following works in VFP8 but _not_ in VFP9:

INDEX ON ALLTRIM(add_adr) TAG add_adr
FIND 'ABC'
---> VFP9 error: "Data type mismatch"

Add_adr is a character field. It's related to the ALLTRIM() in the INDEX expression; without that everything is OK. And, as I said, under VFP8 everything is OK too.

Any ideas?
Rafi

 

[VolkerStamme]

Could reproduce that but FIND is, I quote, "included for backward compatibility. Use SEEK instead.". And SEEK works. Seems they haven't tested that ;-)

Volker/

 

[Mike Lewis]

Rafi,

Yes, Volker's right. The FIND command takes a literal value, not an expression. In other words, if you say FIND Rafi, it would actually look for an index expression of Rafi, whereas if you do SEEK Rafi, it looks inside a variable called Rafi and search on whatever it finds there.

Personally, I haven't used FIND since about 1984, and I can't think of any good reason to do so.

Mike

__________________________________
Mike Lewis (Edinburgh, Scotland)

My sites:
Visual FoxPro (www.ml-consult.demon.co.uk)
Crystal Reports (www.ml-crystal.com)

 

[Dan Freeman]

You also shouldn't use ALLTRIM() in an index expression.

From the help file:

"If you attempt to build an index with a key that varies in length, the key will be padded with spaces. Variable-length index keys are not supported in Visual FoxPro. "

Also see the language in the help file about creating index keys with a length of 0 (a possibility with Alltrim()).

 

[RafiAli]

Thanks everybody. I'd forgotten to mention that the SEEK works where the FIND doesn't. I'll go through all my code and replace them all.
Cheers,
Rafi