I've experienced issues myself with corrupt db's returning errors -
loading them up into to Access and repairing them seems to fix most
cases.
On Thu, 3 Feb 2005 11:57:11 +1100, Matthew Palmer <mp...@he...> wrote:
> On Wed, Feb 02, 2005 at 08:29:03PM +0100, William Maddler wrote:
> > is there any reported problem in working with >1GB .mdb files?
> > I have no problems working with small files.
> > I made some testing with ~10MB files and I was able to list tables,
> > export structures and data.
> > Larger files are "ignored", no tables listed, no data extracted.
> >
> > Any clue?
>
> I'm not an mdbtools hacker, but I don't know of any limitations on larger
> files (and 1GB seems like an odd place to stick a limitation), but in my
> experience mdbtools is less forgiving of MDB corruption than Jet is, and
> larger files do like to get corrupted far more than small files do. I have
> observed corrupted MDB files which don't list any available tables, as well
> as a wide variety of other f**ked up symptoms.
>
> I'd run a complete repair/cleanup over the big files before going too far
> down the path of looking for size-limit bugs in mdbtools.
>
> - Matt
>
>
>
|
