Hi Walter.

>After I marked the database readonly the same view was loaded in 0.20 seconds. It makes sense that it should be faster since the database can be cached in the workstation, though I was stunned in the performance difference.

I bet it isn't caching (or at least not entirely), but rather locking. As Cindy mentioned, VFP locks the view records in the DBC every time you open the view; in a read-only DBC, I'm guessing it doesn't bother doing that since the view definition can't change.

>My question is, has someone found problems or bugs when using readonly databases ?

Assuming you're not using offline view (which would need a writable DBC), the only thing I can think of that could possibly be an issue is transactions. I haven't tested this, so it might not be an issue at all, but I think the DBC is used to temporarily store information while a transaction is in progress. It might be that the information is actually stored in an in-memory cache of the DBC rather than the physical file on disk, so, as I said, this may not be an issue at all.

Doug