>Hi Hilmar,
>
>Using IDX indexes (create with INDEX ON ... TO somefile.idx) is unneeded you can use structural indexes (created with INDEX ON ... TAG someTag) which are automaticly released when the view is released.
>
>Using IDX indexes also give problems (errors) when involved with transactions. CDX indexes do not suffer from this limitation.
I see. It seems I should recommend CDX, then. Well, as I mentioned, in my case it is the third-party framework that takes care of these details. It works something like this:
Each form can be based on tables, or on views.
To allow the user to sort on any column, temporary indices (IDX) are created.
To avoid problems with transactions, under certain circumstances (mainly, when the user starts editing, I believe), an application-object method is invoked, that deletes temporary indices in ALL open forms. This means that the user looses the current sort order (if it is based on a temp index). An option exists to automatically rebuild the temp index in the current form, but this, of course, makes everything slower (especially for large tables).
Hilmar.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)