Walter,

I'm not sure at all about readonly databases. What I do know is that a lot of developers have a local copy of a DBC that contains views only on each machine. That avoids the problem of two users needing to lock the DBC in order to read the view definition.


>I just discovered a major difference in performance when using local view in a multiuser network environment from a readwrite or readonly database.
>
>A particular view takes about 1.4 seconds to open (NODATA). This is caused by the massive view definition that has to read from the database. Since the database is not readonly, the view definition is read entirely from the database each time it is loaded.
>
>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. This made me wondering why I should not mark my database readonly because in most of my applications the database definition never changes since for updates I place a new database and append the table data from the old one.
>
>My question is, has someone found problems or bugs when using readonly databases ?
>
>Walter,