We have been putting all Views into separate views only DBCs for the purpose of avoiding locking contention when VFP locks the DBC header to do a Requery. This worked fine in VFP6. However VFP7 chokes when Indexing a view if the DBC is Read Only.
To reliably reproduce, create a DBC with only Views in it, set the Read Only property in Windows Explorer, and try to Index the View.
I know index info is stored in the DBC and for a table it must be maintained in the DBC file. However, View indices are not persistent, so "writing" to the cursor in memory should be sufficient without trying to write it to the DBC file on disk. VFP6 had this right IMO, VFP7 has it wrong, and it should be fixed in a SP.
Comments from the Fox team ????
Steve Buttress, MCP
ProMatrix MVP - Life
ProSysPlus Developer