mdb-export segfault when OLE field

Hi,

I'm trying to script a migration of an M$ Access db to PosgreSQL.  The
db has tables where some fields contain OLE objects.  These are causing
mdb-export to segfault.  However, if I export the table from "gmdb2
0.6pre1", the table is exported fine, although the OLE object links in
the respective cells are replaced by garbage characters.  I really don't
care about those fields, and am ok with replacing those with an empty
string, which could be done by post-processing the output with other
tools.  However, how can I emulate "gmdb2 0.6pre1" behaviour so that the
table is completely exported?  I presume it uses mdb-export with some
appropriate combination of switches, but I can't figure out which.  Any
help would be appreciated.


Cheers,

-- 
Seb


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/