>I have view definitions in the dictionary that are run in the app and then indexed with the following command after selecting the proper view.
>
>INDEX ON &lcIndex TAG &lcTag ADDITIVE
>
>I do believe that this is supposed to create a structural index file with the same name as the table or in this case, the view. These views are not used for updating anything at this point and are used to locate specific records for a user. After the user has found the specific record, then performed an update (on the buffered table), I'm finding that the BEGIN TRANSACTION causes an error with the message;
>
>V_??? (viewname) has one or more non-structural index files open.
>
>This is with private datasessions, but the mystery is how is it that non-structural indexes are being created for these views with a structural index command? I need to get rid of this.
>
>Thanks,
>Steve Despres

Additive is used when creating non-structural indexes. And form VFP Help, Additive means that all other open non-structural indexes will be left open when the new non-structural index is created. If Additive is omitted, all open non-structural index files will be closed. Any structural index will, of course, remain open. Can a view really have a structural index? I tried this once, and the next time I opened my database and the view, it corrupted my .DBC. I have avoided them ever since.