Hi Chad:

I can answer your question in the following context. To use DefineTag, it must operate on an index tag, period. If you are pulling in a restricted data set from a SQL server table, I can see why you wouldn't generally need to create an index on the result set. But, DefineTag need an index so, if you want to use this method, you need to create as many indexes as you require for the defined tags that appear in the lookup dialog. As to the type of index, that's up to you but, any normal VFP index tag will do.

>Gary,
>
>Thanks for the reply. It's not that "obvious" because for many of my searches, I don't create indexes on the cursors. Speed hasn't been a problem yet. Does the name search require an index tag? If so, does it have to be a special index? Which fields? NormalizeString()? One field? All fields of the name components?
>
>Thanks
>
>>Hi Chad:
>>
>>You call the DefineTag method by subclassing the cmLookUpManager::GenTagList method. The default code scans the indexes on the cursor. If you dont want that, you specify your own DefineTag calls. Obviously, there needs to be indexes created on the cursor :)
>>
>>>I'm trying to add searching (via the frmFindDialog) to a composite name field (cPrefix, cFirst, cMiddle, cLast, cSuffix). In the GenTagList, I can't figure out how to successfully call the DefineTag method. The cursor is from a remote view of a SQL Server table.
>>>
>>>Any ideas?