>Thanks for your response. Thought I'd let you know what the problem turned out to be.
>
>As you probably know, when you create a view VFP assigns a unique filename to the "table". When you create an index on that view, VFP creates a filename for the index such as [uniquefilename.tag]. If I run the form from command window and open the data session and select the view and go to the command window and issue "?dbf()", I see something like C:\TEMP\789X008K.TMP. If I look at the properties for the view and the Index Order pull-down, I'll see files like: 789x00k.Title and 789x00k.Composer. Since the filenames are all the same, these are structural indexes. Everything's cool.
>
>When, however, I requery the view, VFP assigns a new unique filename to the view table. Interestingly, the previous index files are retained. When I first discovered that, I thought "Cool, I don't have to recreate the indexes.". The problem is that these older index files are now considered non-structural indexes because they no longer have the same filename as the view/table and that's why I was getting the 1548 error stating that non-structural indexes were open. I did not go to the effort of determining whether or not VFP updates those index files after the requery or whether they still contained pointers to the old data (potentially ugly!), but that's kind of moot given the error and the resulting need to recreate the indexes.
>
>The solution, of course, is to issue a DELETE TAG ALL before doing the requery and then rebuild the indexes.
>
>Thank you both for your input.

Thanks for sharing this info, Peter.