When we upgraded to VFP7 I had to free all of the tables from the DBC just to keep the application working.

It turns out that the DBC changed from VFP6 to VFP7. Our application is a read-only reporting tool reading tables of millions of records. To enhance performance, I was creating temporary indexes (non-structural) on the tables to display data. In VFP6 this was no problem, but in VFP7 this no longer worked. Apparently the DBC in VFP7 wants to keep track of all indexes, even .idx indexes, not just structural indexes. If the DBC is read only (as is MUST be on a CD-ROM) it can't be updated and can't keep track of new indexes.

I posit that this is a bug, as it is unexpected and undocumented behavior, but I haven't had any luck getting Microsoft to respond to my queries.

My guess is they had to change the DBC to support database events...but nobody seems to know.

>I rewrote my companies major product in VFP6 and now in VFP7 using the