[mdb-dev] Re: A valid Access mdb that crashes all the mdbtools?

[Dan T. <da...@li...>]

Hi list.  I'm new.

a while ago (2002-06-08 02:41) ken wrote:
     I've seen some strange problems with all of the mdb tools (except =
mdb-dump and
    mdb-ver) on a fairly generic access file.
    =20
     mdb-ver reports that it is a "JET3" database. I find that odd =
because I believe it was
    created with Access2000, or at very least was created with Access97 =
and then upgraded to
    Access2000.
    =20
     The file is large (1036288 bytes) and the only odd thing is that =
there is a .ldb file to go
    with it. I am totally ignorant of Access and mdb/ldb files; I just =
want to get the data out
    of these damned things and into mysql.
    =20
     The backtrace of mdb-tables (cvs from tonight) is: <snip>
I'm having the same problem - if you run the DB through the =
encrypt/decrypt function in Access it seems to fix it. (And viewing the =
before/after files with Wordpad reveals that mdbtools crashed when the =
DB was encrypted.)  Does mdb-tools have any support for encrypted =
databases?

My (other) problem is this: after decrypting the database, mdb-export =
pumps out an empty string for one of the fields (mdb-schema identifies =
the field as a 6 character text field, which has data when viewed in =
Access).  The field happens to be the last field... has anyone ran into =
this problem before?

Dan