> > > Yes, I found that with the select(viewless) cursor that I generated, I > could not create more than one index tag, nor could I change the tag once > it was created, for the CDX file with the same temporary name as the > cursor (I got a "read only file" error). This causes me to use the "index > on whatever tag whatever of somefile" which file I have to erase when I'm > done. I don't think so - any index on a cursor (whatever the source and way of creating it) vanishes when the cursor is closed. Still, I didn't check this for VFP (I think it defaults to FP behaviour), but if it didn't work I would have found tons of dead .cdx'es on my disk by now. I simply forget to delete them - if VFP closes cursors, their indexes vanish. > With a view cursor I can create multiple indexes using the temp cdx > filename, and it just goes away when I'm done, I don't have to erase it > myself. So with these restrictions on select cursors, what is the > advantage of using a select statement over a view? Are selects faster? > Originally I was having troubles with parameters, but those problems have > been solved, or at least I hope they have! So what is the advantage? To be honest, I haven't tried views yet. If they are just stored SQL commands (something like saved queries) as I believe they are, then they create cursors all the same, and all of this applies.