B
Brad Wood
Closest related newsgroup I could find...
I am using DAO to programmatically create an access database, close it, set
the file properties to read only, and re-open it.
Upon attempting to reopen the database after making it read only, I get the
Jet access error "Jet database engine cannot open the file" ... "it is
already opened exclusively" ...
If I attempt to open the same file directly with Access, I get the error
"database or object is read-only." If I remove the read only property from
the file and open it in Access, it opens fine. If I make the file read only
again and open it directly in Access it opens fine (in read only mode).
I hope somebody has some idea why the file is in such a weird state when I
set it read only programatically. Note: this is unrelated to MS KB article
191737 - Access / DAO is able to create a .ldb file in the same folder.
I am using DAO to programmatically create an access database, close it, set
the file properties to read only, and re-open it.
Upon attempting to reopen the database after making it read only, I get the
Jet access error "Jet database engine cannot open the file" ... "it is
already opened exclusively" ...
If I attempt to open the same file directly with Access, I get the error
"database or object is read-only." If I remove the read only property from
the file and open it in Access, it opens fine. If I make the file read only
again and open it directly in Access it opens fine (in read only mode).
I hope somebody has some idea why the file is in such a weird state when I
set it read only programatically. Note: this is unrelated to MS KB article
191737 - Access / DAO is able to create a .ldb file in the same folder.