mdbtools-dev

[mdb-dev] Column names getting cut off

[Camden D. <cd...@gm...>]

Hello list.  For a project I'm developing I need to access a live mdb
database to pull some data and utilize it in a php app on a linux box.
 Since the data need to be 'live', I can't simply export the mdb to
another format; I have to access it as an mdb.

Currently, I'm trying to use mdbtools, mdbtools-odbc, and unixodbc. 
I've tried using the rpms for version 0.5-1 and 0.5-236 of the
mdbtools packages, and version 2.2.8-55 of unixodbc.

Everything installs fine, and I can connect to my mdb just fine.  The
mdb is Jet 4 and about 200 megs large, and contains a few dozen
tables.  I can access most of the tables just fine.  However, the one
that I actually need doesn't come through correctly.  When I use
mdb-sql to do a 'describe table' on it, about the first 20 columns
come through find, but then the next 80 or so columns are completely
blank.  The one between the ones that work and ones that don't is cut
off, with only half the column name showing up.  The ones with blank
column names still have their type and size displayed correctly, so
it's kind of being read correctly.

I've looked at the table in Access, and nothing seems very strange
about that particular column.  My tables and column names do contain
underscores, but as it works with other tables that have underscores,
I don't think that's the issue.  I tried the 'compact and repair
database' option in Access as well, but that didn't fix it.

I tried compiling the 0.6 version of mdbtools, but it can't read any
of the tables in my database.  I tried the cvs version as well, but
couldn't get it to even compile correctly.

Any help would be greatly appreciated.
-Camden Daily

[mdb-dev] Column names getting cut off

[EverythingAccess.com S. <wa...@ev...>]

 >Hello list.  For a project I"m developing I need to access a live mdb
 >database to pull some data and utilize it in a php app on a linux box.
 > Since the data need to be "live", I can"t simply export the mdb to
 >another format; I have to access it as an mdb.
 >
 >Currently, I"m trying to use mdbtools, mdbtools-odbc, and unixodbc.=20
 >I"ve tried using the rpms for version 0.5-1 and 0.5-236 of the
 >mdbtools packages, and version 2.2.8-55 of unixodbc.
 >
 >Everything installs fine, and I can connect to my mdb just fine.  The
 >mdb is Jet 4 and about 200 megs large, and contains a few dozen
 >tables.  I can access most of the tables just fine.  However, the one
 >that I actually need doesn"t come through correctly.  When I use
 >mdb-sql to do a "describe table" on it, about the first 20 columns
 >come through find, but then the next 80 or so columns are completely
 >blank.  The one between the ones that work and ones that don"t is cut
 >off, with only half the column name showing up.  The ones with blank
 >column names still have their type and size displayed correctly, so
 >it"s kind of being read correctly.
 >
 >I"ve looked at the table in Access, and nothing seems very strange
 >about that particular column.  My tables and column names do contain
 >underscores, but as it works with other tables that have underscores,
 >I don"t think that"s the issue.  I tried the "compact and repair
 >database" option in Access as well, but that didn"t fix it.
 >
 >I tried compiling the 0.6 version of mdbtools, but it can"t read any
 >of the tables in my database.  I tried the cvs version as well, but
 >couldn"t get it to even compile correctly.
 >
 >Any help would be greatly appreciated.
 >-Camden Daily

=20

I=92m not part of the development team here or anything but I can tell =
you
what the problem is so that one of the developers can fix it.

=20

The problem is that Table Definition pages can span over several Jet =
pages,
but I would suggest that the mdb-tools suite doesn=92t support this yet. =
 I am
fairly certain your problem listed above is due to this as the field
definitions (such as size, type etc) are listed in the table definition
pages well before the field names.  I also recognize this from my =
companies
Access recovery software when we were initially writing it.

=20

Technical details;

=20

A 4-byte value exists at offset 4 in each Table Definition page.  This
pointer will be blank unless this is a multi-page table definition.  If =
it
is a multi-page table definition, this 4 byte value is a pointer to the =
next
overflow table definition page (note: you could theoretically have many
spanned pages for each table definition).

=20

So the mdb-tools software simply needs to attach these =91extension=92 =
pages
when reading the first table definition page.  Each extension page =
contains
PageSize-8 (jet4: 4088, jet3: 2040) bytes of data which should be =
appended
to the tdef data before it is processed. =20

=20

Regards,

=20

Wayne Phillips=20

HYPERLINK =
"http://www.EverythingAccess.com"http://www.EverythingAccess.com =96
Professional Access Database Repair Service, free utilities and forums

=20

=20


--=20
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.7.0 - Release Date: 08/03/2005
=20

Re: [mdb-dev] Column names getting cut off

[Sam M. <pa...@gm...>]

Tried repairing your access database using the access repair utility?

access databases are remarkably fragile - they're the only databases
i've needed to use repair facility on a semi-regular occaision.

Sam

On Thu, 24 Feb 2005 10:52:46 -0600, Camden Daily <cd...@gm...> wrote:
> Hello list.  For a project I'm developing I need to access a live mdb
> database to pull some data and utilize it in a php app on a linux box.
>  Since the data need to be 'live', I can't simply export the mdb to
> another format; I have to access it as an mdb.
> 
> Currently, I'm trying to use mdbtools, mdbtools-odbc, and unixodbc.
> I've tried using the rpms for version 0.5-1 and 0.5-236 of the
> mdbtools packages, and version 2.2.8-55 of unixodbc.
> 
> Everything installs fine, and I can connect to my mdb just fine.  The
> mdb is Jet 4 and about 200 megs large, and contains a few dozen
> tables.  I can access most of the tables just fine.  However, the one
> that I actually need doesn't come through correctly.  When I use
> mdb-sql to do a 'describe table' on it, about the first 20 columns
> come through find, but then the next 80 or so columns are completely
> blank.  The one between the ones that work and ones that don't is cut
> off, with only half the column name showing up.  The ones with blank
> column names still have their type and size displayed correctly, so
> it's kind of being read correctly.
> 
> I've looked at the table in Access, and nothing seems very strange
> about that particular column.  My tables and column names do contain
> underscores, but as it works with other tables that have underscores,
> I don't think that's the issue.  I tried the 'compact and repair
> database' option in Access as well, but that didn't fix it.
> 
> I tried compiling the 0.6 version of mdbtools, but it can't read any
> of the tables in my database.  I tried the cvs version as well, but
> couldn't get it to even compile correctly.
> 
> Any help would be greatly appreciated.
> -Camden Daily
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> mdbtools-dev mailing list
> mdb...@li...
> https://lists.sourceforge.net/lists/listinfo/mdbtools-dev
>

Re: [mdb-dev] Column names getting cut off

[Camden D. <cd...@gm...>]

I tried using the "compact and repair" function in Access, but it
still has the same problem.

Can anyone suggest any other good tools/methods for fixing an mdb file
that may be corrupted?

-Camden Daily

On Fri, 25 Feb 2005 22:28:10 +1000, Sam Moffatt <pa...@gm...> wrote:
> Tried repairing your access database using the access repair utility?
> 
> access databases are remarkably fragile - they're the only databases
> i've needed to use repair facility on a semi-regular occaision.
> 
> Sam
> 
> On Thu, 24 Feb 2005 10:52:46 -0600, Camden Daily <cd...@gm...> wrote:
> > Hello list.  For a project I'm developing I need to access a live mdb
> > database to pull some data and utilize it in a php app on a linux box.
> >  Since the data need to be 'live', I can't simply export the mdb to
> > another format; I have to access it as an mdb.
> >
> > Currently, I'm trying to use mdbtools, mdbtools-odbc, and unixodbc.
> > I've tried using the rpms for version 0.5-1 and 0.5-236 of the
> > mdbtools packages, and version 2.2.8-55 of unixodbc.
> >
> > Everything installs fine, and I can connect to my mdb just fine.  The
> > mdb is Jet 4 and about 200 megs large, and contains a few dozen
> > tables.  I can access most of the tables just fine.  However, the one
> > that I actually need doesn't come through correctly.  When I use
> > mdb-sql to do a 'describe table' on it, about the first 20 columns
> > come through find, but then the next 80 or so columns are completely
> > blank.  The one between the ones that work and ones that don't is cut
> > off, with only half the column name showing up.  The ones with blank
> > column names still have their type and size displayed correctly, so
> > it's kind of being read correctly.
> >
> > I've looked at the table in Access, and nothing seems very strange
> > about that particular column.  My tables and column names do contain
> > underscores, but as it works with other tables that have underscores,
> > I don't think that's the issue.  I tried the 'compact and repair
> > database' option in Access as well, but that didn't fix it.
> >
> > I tried compiling the 0.6 version of mdbtools, but it can't read any
> > of the tables in my database.  I tried the cvs version as well, but
> > couldn't get it to even compile correctly.
> >
> > Any help would be greatly appreciated.
> > -Camden Daily
> >
> > -------------------------------------------------------
> > SF email is sponsored by - The IT Product Guide
> > Read honest & candid reviews on hundreds of IT Products from real users.
> > Discover which products truly live up to the hype. Start reading now.
> > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> > _______________________________________________
> > mdbtools-dev mailing list
> > mdb...@li...
> > https://lists.sourceforge.net/lists/listinfo/mdbtools-dev
> >
>

Re: [mdb-dev] Column names getting cut off

[Jeff S. <why...@ya...>]

--- Camden Daily <cd...@gm...> wrote:
> Everything installs fine, and I can connect to my mdb just fine.  The
> mdb is Jet 4 and about 200 megs large, and contains a few dozen
> tables.  I can access most of the tables just fine.  However, the one
> that I actually need doesn't come through correctly.  When I use
> mdb-sql to do a 'describe table' on it, about the first 20 columns
> come through find, but then the next 80 or so columns are completely
> blank.  The one between the ones that work and ones that don't is cut
> off, with only half the column name showing up.  The ones with blank
> column names still have their type and size displayed correctly, so
> it's kind of being read correctly.

'Describe table' sets up a temporary table to store the information.
IIRC, temporary tables were still severely limited as of version 0.5.

> I tried compiling the 0.6 version of mdbtools, but it can't read any
> of the tables in my database.  I tried the cvs version as well, but
> couldn't get it to even compile correctly.

I'm not sure what the problem with 0.6pre1 would be.

I am curious as to why the cvs version is not compiling for you.  Can
you give some more information on that?

 -- Jeff Smith



		
__________________________________ 
Do you Yahoo!? 
Yahoo! Mail - 250MB free storage. Do more. Manage less. 
http://info.mail.yahoo.com/mail_250

Re: [mdb-dev] Column names getting cut off

[Camden D. <cd...@gm...>]

> 'Describe table' sets up a temporary table to store the information.
> IIRC, temporary tables were still severely limited as of version 0.5.

It's not just the 'describe table' command that has problems.  If I
try to select any of the column names that do show up, it works fine. 
If I try to use one of the column names that doesn't show up, I
recieve a column not found error.

Here's an example of what I'm getting from my describe tables:
...
|CoBrokeAgent   |Text                |100      |
|CoBrokeNotn     |Text                |30       |
|CoBrokePer      |Single              |4         |
|C                     |Boolean           |0         |
|                       |Text                 |6         |
|                       |Currency           |8         |
...
with all the columns before that point showing up fine, and being
queryable, but all the columns after that totally inaccessible.  It's
also cutting off the full name of the column displayed as 'C'.

> I am curious as to why the cvs version is not compiling for you.  Can
> you give some more information on that?

I think it was just a lot of issues with automake and autoconf not
doing something correctly.  I'm using Suse 9.1, and had all the rpms
installed, but it still threw up lots of errors when I tried to
configure it.  If there have been significant changes to the code
since 0.5, maybe I'll try compiling the CVS again.

-Camden