Hi doug,

>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.

I've done a little test on the command window. Just typed BEGIN TRANSACTION, did a cascade delete and cascade update in various tables and type ROLLBACK. The changes rolled back perfectly, so I guess this would be safe.

I've noted the TransactionLog record (2nd record) in the database too. But since on the network several transactions can be active at the same time, I don't think this record is use for this, unless the record is buffered and the changes in the log only exist in memory.

Walter,