Hi Mark,

Our framework handles local and remote views differently, or I would just use the same syntax. I'll probably have to check if the view is a remote view, and if so, add the "%" to the variable as you described. I could have sworn the remote view worked as is a year ago, and that's the main reason for my question. Do you know how Oracle would handle a ''+'%' as in my example? Thanks.

>Why don't you just have LIKE ?cLastName, etc. in the WHERE clause then set cLastName = alltrim(ThisForm.txtLastName.Value) + "%"
>

>>Hello everyone,
>>
>>About year ago or so , I set up a name search view that looked sorta like this:
>>
>>Local View:

Select * from People where LastName = ?cLastName and FirstName = ?cFirstName

>>Remote View:

Select * from People where LastName Like ?cLastName+'%' and FirstName Like ?cFirstName+'%'

>>
>>The intent was to provide search capability with only partial names, while not hard-coding percent signs (%) for remote views. To see everyone whose last name started with "S", I would simply set the cLastName variable to 'S'. To my recollection, this used to work as expected on both local and remote views. Now, if I set cFirstName to an empty value (''), the remote view only returns records with an empty FirstName field. If I set cFirstName to '%', then it does work as expected, but as I said earlier, I'm trying to avoid doing that in code. Evidently, SQL Server sees FirstName=''+'%' differently than FirstName='%'. Is there a SQL Server setting somewhere that would affect this? I would probably just use the LIKE keyword in the Local View and put the '%' in code, but our framework is expecting the view to be in the format above.
>>
>>We are currently using SQL Server 7 Standard version with the latest service pack. Previously, I was using the Desktop version, and probably with an older service pack. Maybe it is my memory that is defective <g>, but an indication either way would be appreciated.
>>
>>Thanks.