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.
>Good Friday Morning to All,
>
>I ran into a problem using <> operator where the following happens:
>
>cTest1 = "This is a sample string"
>cTest2 = "This is a sample string test"
>? cTest2 <> cTest1
>
>
>Now I am thinking if I should do away with using <> operator because it always relies on SET EXACT ON and just use "==" in ALL my comparisons. What do you think?
Groet,
Peter de Valença
Constructive frustration is the breeding ground of genius.
If there’s no willingness to moderate for the sake of good debate, then I have no willingness to debate at all.
Let's develop superb standards that will end the holy wars.
"There are three types of people: Alphas and Betas", said the beta decisively.
If you find this message rude or offensive or stupid, please take a step away from the keyboard and try to think calmly about an eventual a possible alternative explanation of my message.
