Icon View Incident Report

Serious Serious
Reported By: Roy Lambert
Reported On: 3/28/2009
For: Version 2.02 Build 10
# 2968 Creating a Database with an Invalid Path Can Cause Database to Become Read-Only

Use the following steps to recreate the issue:

1. Pick a session in EDBManager which has the existing database.

2. Create a new database with the path almost pointing to it. Keep the directory structure correct but have a different disk identifier, one that soen not and can not exist on your machine - eg my real path is E:\HH Dev\TfR\NLH so I used Q:\HH Dev\TfR\NLH (I have no Q drive)

3. Try and open a table under the this database you get the following error

ElevateDB Error #600 File manager error (Cannot create file q:\hh dev\tfr\nlh\EDBDatabase.EDBCat (OS Error: The system cannot find the path specified.))

4. Alter the database path to the real one

5. Open one of the tables and it's read only


Comments Comments and Workarounds
The issue was caused by the lock manager treating a database as read-only if the database path was non-existent. EDB now reports an error when trying to open a database with an invalid path.


Resolution Resolution
Fixed Problem on 3/29/2009 in version 2.02 build 11


Products Affected Products Affected
ElevateDB Additional Software and Utilities
ElevateDB DAC Client-Server
ElevateDB DAC Client-Server with Source
ElevateDB DAC Standard
ElevateDB DAC Standard with Source
ElevateDB DAC Trial
ElevateDB LCL Standard with Source
ElevateDB VCL Client-Server
ElevateDB VCL Client-Server with Source
ElevateDB VCL Standard
ElevateDB VCL Standard with Source
ElevateDB VCL Trial

Image