I can't answer for MS but it does seem to me that there is a 'design reason' for this behaviour... dBase, on which VFP is originally modelled, works that way.

You can, as shown by others, use the "==" or the SET EXACT ON statement to get the behaviour you (think) you want. Be aware, though, that for SQL commands like SELECT - SQL you must use SET ANSI ON to get the equivalent.

being able to compare partial strings is VERY handy, however, so you want to think hard before you make this your 'standard'. I think you'll find lots of developers work with EXACT OFF most of the time, setting it ON only briefly if needed.

cheers

>Is this a Bug from VFP? or there is a design reason for this behavior