Correct and efficient are not the same thing. Correct gets you the desired result. Efficient gets you the correct result faster, with fewer resources, or both.

>Hi Craig
>
>I often feel that correct has to mean the best possible choice and so efficiency enters into it. As Fabio pointed out, if you travel from Utah heading East, when you meant to go West, it might be the correct way if, you wanted to pick up someone/something to the East before going West. If that is not your scenario, then going East first is clearly incorrect.
>
>If you were hammering nails and missing most of the time and bending many nails, you may be getting the job done, but no one would say you're doing it correctly.
>
>In fact, option a below CANNOT be correct! It's missing "FOR UPPER(LastName+FirstName) =".
>
>I'd say option c would be the correct way to find one particular name. The clarification of the request - do they want one name, are they looking for duplicates will refine the scenario so I could choose the correct option.
>
>If they want a list of all customers with that name, I'd probably argue for an option e
>
>lcFullName = UPPER(m.LastName + m.FirstName)
>SELECT * FROM Customers WHERE UPPER(LastName + FirstName) = m.lcFullName
>
>If, like Terry Thurber, I wanted to populate a listbox I might choose option f
>
>SET ORDER TO TAG FullName
>m.lcFullName = UPPER(m.LastName + m.FirstName)
>SEEK m.lcFullName
>DO WHILE UPPER(LastName + FirstName) = m.lcFullName
> AddItem blah, blah
> SKIP
>ENDDO
>
>Correctness depends on the scenario.
>