View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000469 | CaseTalk Modeler | Repository | public | 2014-04-30 11:05 | 2026-09-01 21:59 |
| Reporter | Marco Wobben | Assigned To | Marco Wobben | ||
| Priority | high | Severity | major | Reproducibility | random |
| Status | assigned | Resolution | open | ||
| Summary | 0000469: Database Locked Error | ||||
| Description | It happened once where edits were unsaved and CaseTalk mentioned a 'database lock or readonly' error. This prevented saving any modification. A 'break a lock' would be a benefitial feature to force changes to be saved. | ||||
| Additional Information | Similar behavour is found in Office tools which recover documents after a crash. It works the other way around, but still leave a door open to recover unsaved changes. | ||||
| Tags | No tags attached. | ||||
| CaseTalk Edition | |||||
| related to | 0000878 | closed | Marco Wobben | Database IG(G) is locked |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2014-04-30 11:05 | Marco Wobben | New Issue | |
| 2014-04-30 11:05 | Marco Wobben | Status | new => assigned |
| 2014-04-30 11:05 | Marco Wobben | Assigned To | => Marco Wobben |
| 2026-09-01 21:59 | Marco Wobben | Relationship added | related to 0000878 |
