Erich S.

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

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