It sounds like you need a new contractor. <s>

While the Search method may not be optimizable in the Rushmore sense, it will definitely be faster than querying each binder for its name properties. You can also the GetDocumentByKey method of a view. Find (or create) a view that has a list of the binders. You can do a search based on the columns marked as Sorted.

See http://www-12.lotus.com/ldd/doc/domino_notes/5.0.3/help5_designer.nsf/f4b82fbb75e942a6852566ac0037f284/75b48a3b93ae813e8525687e00598639?OpenDocument&AutoFramed.

Because views build indexes, this will be optimized.

HTH.

>Hi Larry,
>
>I am going to try your code for instantiating a Notes object but one question from the below - in talking to our Notes developer (contractor), he does not think that the query would be optimized in any way because he said that "indexes cannot be attached to a field like in VFP". I had assumed that if it was an ODBC driver that the driver would use whatever indexes it could find. What do you think - optimized or not?
>
>Albert,
>
>1) The Notes ODBC driver does support the basic SQL query syntax. Using SPT or remote views, you can query on a view and the result set will be returned as a VFP cursor. You can also use the object model and return a document collection and parse through that. The query would be optimized within Notes so the major processing would be done going through the collection.