Jess,

I think you are being overly sensitive here - If the key is UPPER(xxxx) then it is written that way at index build time (ie *not* when you do the seek) and if you do SEEK UPPER(yyyy) then the UPPER is done *outside* (before) the "query".

So the alleged slowdown is highly marginal.

Cheers,
Jim N

>>>>Hi,
>>>>
>>>>Im using the seek command to seek a client name in a very large database with 1.7 m records. i have set the order to name2 which is the clients surname and then using the command SEEK locclient. loc> >
>>>>Please help
>>>>
>>>>thanks
>>>>~Quinn
>>>
>>>If you are not receiving an error, say, 'Index tag not found', then try to check the length of the name and compare it to the length of the clocvariable.
>>>
>>>Include this on the syntax valid event of the textbox control:
>>>
>>>SELECT table1
>>>nLength = FSIZE('fieldname')
>>>cLocVariable = STR(Thisform.TextBoxName.Value,nLength,0)
>>>=SEEK(cLockVariable,'Table1','FieldnameTag')
>>>
>>You may need to set your index to UPPER(sirname) and do your seek
>>with UPPER(variable) so they match exactly
>>./
>>Andy Roth
>>andyroth@electriciti.com
>
>Andy,
>It will, but it may affect the speed during query. IMHO, it is better to use SET NEAR ON , SET EXACT OFF to get to the nearest data that matches the seek string as long as you have the proper length of the variable and fields, proper index tag name, and table.