From: Chris C. <cc...@fi...> - 2011-04-11 12:27:56
|
Hi Jakob, On 09/04/11 02:07 AM, Jakob Egger wrote: > Dear Chris, > Are you really sure that you are using the patched version of MDB > Tools? Maybe you have some library issues: it could be that you still > have an old version of libmdb somewhere, and that mdb-export > dynamically links against that old version. Maybe you need to type > "make install" to install the new library after compiling? (Note: I > use my custom build script for libmdb, so I'm not sure how you're > supposed to compile mdb tools) > > for debugging, try "which mdb-export" to make sure you are calling > the newly compiled version of mdb-export. then try > "ldd /usr/bin/mdb-export" to find out against which libmdb it is > linked. Then check the linked "libmdb" file's creation date. The problem was indeed the libraries - I'm using a Debian system at work, and they've split the mdb-tools package into many pieces (mdbtools, mdbtools-dev, libmdbtools, libmdbodbc). I had removed the packaged version of mdbtools but didn't remove libmdbtools. After having cleaned out the packaged library files, all the data files are interpreted correctly. Thanks again! I use Slackware at home and generally don't have to deal with issues like this, since Slackware tends to package everything together (or you just build it yourself anyway). -- Chris Craig Software Developer Fibernetics Corp 605 Boxwood Dr Cambridge ON N3E 1A5 519-489-6700 x 753 |