I'm using UCanAccess 4.0.2 to work on an encrypted MS AccessDB.
First "problem":
The DB ist enrypted (abc.mdb + xyz. ldb). When establishing the connection I deliver a wrong password via properties. But nevertehless I am able to open the connection and read / write some tables without problems :-o
Why??
Next problem: One table delivers an error while connecting to the database:
"WARNING:Detected Not Null constraint breach, table xyz, record Row[383:3][{...}]: making the table xyz readonly"
My question: How is the information "[383:3]" to be interpretated? Is there a way to detect which column produces the error?
The problem is: When I open MS Access there are only few columns with "not null" restriction ("required=yes"). But the record shown in the error message got values for these columns...
Any help is appreciate!
Greetings
Erich
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I discover one problem by myself:
Yes, the database has errors. One column obviously got the atttribute "required=yes" afterwards, although existing data violates that constraint. But the error message is absolutely misleading, because the reported record has nothing to do with this error. :-(
I guess it's a (little) bug ( - not a feature). It would be very nice if the correct record and the causing column would be shown.
The first problem continues to exist: I'm able to read/write an encrypted .mdb although using a wrong password or even passing no password property.
Perhaps you've tried this already, but I know I've run into this "user
error" myself in the past: are you sure that your settings there are the
one actually being used by ucanaccess? That is, if you try changing the
file location specified, does it still "work"?
I discover one problem by myself:
Yes, the database has errors. One column obviously got the atttribute
"required=yes" afterwards, although existing data violates that constraint.
But the error message is absolutely misleading, because the reported record
has nothing to do with this error. :-(
I guess it's a (little) bug ( - not a feature). It would be very nice if
the correct record and the causing column would be shown.
The first problem continues to exist: I'm able to read/write an encrypted
.mdb although using a wrong password or even passing no password
property.
File file = new File("d:/tmp/myTest.mdb");Properties props = new Properties();props.setProperty("JackcessOpener", "de.myproject.CryptCodecOpener");// props.setProperty("password", "password");props.setProperty("Showschema", "false");props.setProperty("Memory", "true");Connection conn = DriverManager.getConnection("jdbc:ucanaccess://" + file, props);
Any idea? Or is it a feature - not a bug ;-)
Erich
I discover one problem by myself:
Yes, the database has errors. One column obviously got the atttribute
"required=yes" afterwards, although existing data violates that constraint.
But the error message is absolutely misleading, because the reported record
has nothing to do with this error. :-(
I guess it's a (little) bug ( - not a feature). It would be very nice if
the correct record and the causing column would be shown.
The first problem continues to exist: I'm able to read/write an encrypted
.mdb although using a wrong password or even passing no password
property.
File file = new File("d:/tmp/myTest.mdb");Properties props = new Properties();props.setProperty("JackcessOpener", "de.myproject.CryptCodecOpener");// props.setProperty("password", "password");props.setProperty("Showschema", "false");props.setProperty("Memory", "true");Connection conn = DriverManager.getConnection("jdbc:ucanaccess://" + file, props);
Any idea? Or is it a feature - not a bug ;-)
Erich
Hello,
I'm using UCanAccess 4.0.2 to work on an encrypted MS AccessDB.
First "problem":
The DB ist enrypted (abc.mdb + xyz. ldb). When establishing the connection I deliver a wrong password via properties. But nevertehless I am able to open the connection and read / write some tables without problems :-o
Why??
Next problem: One table delivers an error while connecting to the database:
"WARNING:Detected Not Null constraint breach, table xyz, record Row[383:3][{...}]: making the table xyz readonly"
My question: How is the information "[383:3]" to be interpretated? Is there a way to detect which column produces the error?
The problem is: When I open MS Access there are only few columns with "not null" restriction ("required=yes"). But the record shown in the error message got values for these columns...
Any help is appreciate!
Greetings
Erich
Hello,
I discover one problem by myself:
Yes, the database has errors. One column obviously got the atttribute "required=yes" afterwards, although existing data violates that constraint. But the error message is absolutely misleading, because the reported record has nothing to do with this error. :-(
I guess it's a (little) bug ( - not a feature). It would be very nice if the correct record and the causing column would be shown.
The first problem continues to exist: I'm able to read/write an encrypted .mdb although using a wrong password or even passing no password property.
Any idea? Or is it a feature - not a bug ;-)
Erich
Hey Erich,
Perhaps you've tried this already, but I know I've run into this "user
error" myself in the past: are you sure that your settings there are the
one actually being used by ucanaccess? That is, if you try changing the
file location specified, does it still "work"?
Tom
On Wed, Sep 27, 2017 at 3:39 AM, Erich S. erichs13@users.sf.net wrote:
Hey Erich,
Are you still having this "problem"? That is, you can connect to a
database even with a wrong password?
I'm seeing something similar in my testing, and I'm wondering if I'm
crazy...
Tom
On Wed, Sep 27, 2017 at 3:39 AM, Erich S. erichs13@users.sf.net wrote: