>My default setting is SET EXACT OFF. This is the setting I want to rely on. As a consequence, a routine that sets settings like this one to preferred defaults, is called in the load of a form with a private datasession.
>
>In case I want an exact match, I purposely use ( not a==b ) instead of ( a<>b ).
>
>In one major application we have to maintain, the default is ON. In that case, we consciously have to 'read' all expressions differently.
>
Thank you, Peter.
I guess, being a lazy person <g>, I was looking for a all-inclusive "<>" "exact" operator. That way I would not have to worry about SET EXACT OFF or ON and simply use "==" when comparing for equal and "<==> ((c) Copyright Dmitry Litvak <g>) for not equal.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
