% works, but the field could have be also null.  When I use QBE .. it 
returns everything, when I use SQL % it returns everything EXCEPT NULL 
values

On 5/30/2020 9:42 AM, Bernie van't Hof wrote:
> LIKE operator and wildcard characters.
> 
> % for multiple characters (QBE  ..)
> _ for single character (QBE @)
> 
> e.g. WHERE NameCol LIKE 'Kev%Bake_'
> 
> - Bernie
> On 30/5/20 11:21 pm, Kevin Baker wrote:
>> I'm beginning to replace my QBE queries with SQL and have an issue I 
>> can't seem to figure out.  For many reasons, there are times when a 
>> var I'm passing the the query will equal ".."
>>
>> For example in building a query the user has the option to filter 
>> records for a particular field, if they don't filter any records (they 
>> want them all), the var gets the value of ".."
>>
>> The QBE gets passed this var by use ~gsvar (with gsvar having the 
>> value of ..)
>>
>> I'm not sure what I need to change this to for SQL.  In the SQL query 
>> I would still pass the var ~gsvar, but when gsvar has a value of .. 
>> the query fails.  I tried ANY and ALL, but both of those cause an 
>> error (invalid use of keyword).
>