Peter-

Is it safe to assume that you're not purposefully creating non-structural indices in your code that you're perhaps forgetting to close? I'll assume not.

In that case, have you narrowed the problem down to a specific value for your criteria? Rushmore does sometimes cause ad hoc indices to be created and I would suspect that there is an expression that's causing one to be created.

Just a thought.

>Have an application that uses a local view, definition is:
>
>CREATE SQL VIEW "MUSICCAT" ;
> AS SELECT Musictbl.catalog, Musictbl.composer, Musictbl.title, ;
> ....
> FROM appdata!musictbl musictbl ;
> WHERE &?Criteria
>
>"Criteria" is a PUBLIC variable that is populated before the view is opened. Thus the definition of the view does not change, but the contents presented to each user can vary.
>
>A grid is presented and the user has the option to sort the grid by double-clicking on a column header. The program then creates indexed on the view (INDEX ON UPPER(TITLE) TAG TITLE, for example).
>
>Everything works fine in a stand-alone environment. On a network, however, when adding a new record and issuing a BEGIN TRANSACTION, we get error 1548, indicating that "MusicCat" has a non-structural index open. If the user ignores the error, everything seems to be OK - the new record gets added properly.
>
>Each user runs from a unique workarea on their local hard drive, but sharing a common data directory and DBC.
>
>Wondered if anyone had any idea about what might be going on here.