Hi Tracy

Before I started this thread I tested the same idea you just explained. I must have done something wrong because it did not delete the index so that is why I started the thread. However, I went back and re-tested the code and found that indeed it is deleting the index so it appears most of my concerns have been addressed.

Thanks
Simon


>It appears the indices are deleted when the cursor is closed. Here is my code in the AfterCursorFill event():
>

>LPARAMETERS luseCursorSchema, lNoDataOnLoad, cSelectCmd, lResult
>INDEX ON cursor1.contactname TAG cname
>SET ORDER TO TAG cname
>WAIT WINDOW ORDER('cursor1',1)
>DODEFAULT()
>

>The current tag is correct after running this: contactname
>cursor1 is the cursor created using the cursoradapter on a form. The base table is the customers table from the northwind dbc. The index created is c:\temp\[uniquenumber].cdx and it is deleted automatically when cursor1 is closed.
>
>>Hi Tracy
>>
>>That was what I assumed would have to be done. I just wondered what others had done.
>>
>>Am I missing something or is this an overlooked feature of the cursoradapter class? It seems to me that it should have an array property of index tags and keys that should be created and managed automatically. Including deleting the index file when the cursor is closed.
>>
>>Simon
>>
>>>How about Creating the index in the AfterCursorFill event?
>>>
>>>>Hi
>>>>
>>>>I have been testing out the cursoradapter class and wondered what is the preferred method of handling indexes with these cursor. Since they are created without indexes I will need to create some indexex if I want to use Relations or do an incremental lookup etc. I am thinking that always creating and deleting these indexes may be a performance problem.
>>>>
>>>>At present my framework uses listboxes instead of grids and thus requires at least one index on the PK for each table.
>>>>
>>>>What are peoples thoughts and suggestions on the use of indexes with the cursoradapter class?
>>>>
>>>>Thanks
>>>>Simon