mdbtools-dev

Re: [mdb-dev] mdbtools + unixODBC

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

Serg,

What version of mdbtools are you using?  0.5?  I believe these
particular problems were fixed as of 0.6pre1.

 -- Jeff Smith


--- "S. Streltsov" <str...@ph...> wrote:
> Dear users of Mdbtools,
> 
> I'm looking for your help. That something absolutely strange.
> 
> I'm trying to combine mdbtools + unixODBC for further using by php (through 
> Apache) in order to have an access to MS Access database. It seems that  
> mdbtools works well because one the utility (gmb2) read database with out any 
> problems. 
> 
> After that I'm trying to explore with DataManager my database and DataManager 
> see its name, but then I trying to open it, DataManager give following error 
> message : "[unixODBC] Could not find DSN in odbc.ini". These is my
> /etc/odbc.ini
> 
> [planeta]
> Description = Microsoft Access Database of Dogs
> Driver      = MDBToolsODBC
> Database    = /tmp/1.mdb
> Servername  = localhost
> UserName    =
> Password    =
> port        = 5432
> 
> On the other hand, then I try Configurate this database in ODBCConfig,
> it also has two errors (one after another) "Could not construct a property 
> list for (MDBToolsODBC)"and "General installer error".
> 
> These is my /etc/odbcinst.ini
> 
> [PostgreSQL]
> Description             = ODBC for PostgreSQL
> Driver          = /usr/lib/libodbcpsql.so
> Setup           = /usr/lib/libodbcpsqlS.so
> FileUsage               = 1
>                                                                                 
> [MDBToolsODBC]
> Description             = MDB Tools ODBC drivers
> Driver          = /usr/lib/libmdbodbc.so.0
> Setup           =
> FileUsage               = 1
> CPTimeout               =
> CPReuse         =
> 
> 
> Please recommend me something. How to make them work ???
> I really do not know what I can do. ;-(( 
> 
> Sincerely yours,
> Serg Streltsov.
> 
> University of Cologne.



		
__________________________________
Do you Yahoo!?
Yahoo! Mail is new and improved - Check it out!
http://promotions.yahoo.com/new_mail

[mdb-dev] mdbtools + unixODBC

[S. S. <str...@ph...>]

Dear users of Mdbtools,

I'm looking for your help. That something absolutely strange.

I'm trying to combine mdbtools + unixODBC for further using by php (through 
Apache) in order to have an access to MS Access database. It seems that  
mdbtools works well because one the utility (gmb2) read database with out any 
problems. 

After that I'm trying to explore with DataManager my database and DataManager 
see its name, but then I trying to open it, DataManager give following error 
message : "[unixODBC] Could not find DSN in odbc.ini". These is my
/etc/odbc.ini

[planeta]
Description = Microsoft Access Database of Dogs
Driver      = MDBToolsODBC
Database    = /tmp/1.mdb
Servername  = localhost
UserName    =
Password    =
port        = 5432

On the other hand, then I try Configurate this database in ODBCConfig,
it also has two errors (one after another) "Could not construct a property 
list for (MDBToolsODBC)"and "General installer error".

These is my /etc/odbcinst.ini

[PostgreSQL]
Description             = ODBC for PostgreSQL
Driver          = /usr/lib/libodbcpsql.so
Setup           = /usr/lib/libodbcpsqlS.so
FileUsage               = 1
                                                                                
[MDBToolsODBC]
Description             = MDB Tools ODBC drivers
Driver          = /usr/lib/libmdbodbc.so.0
Setup           =
FileUsage               = 1
CPTimeout               =
CPReuse         =


Please recommend me something. How to make them work ???
I really do not know what I can do. ;-(( 

Sincerely yours,
Serg Streltsov.

University of Cologne.

[mdb-dev] Jet4 index page format notes

[John C. <jf...@MI...>]

HACKING documents the Jet3 format index page only.  Here is
the description of the Jet4 index.

Jet4 index page

1 byte type (0x03 for higher level index, 0x04 for leaf index)
1 byte 0x01
2 bytes free space*
4 bytes parent page
4 bytes 0x00000000
4 bytes previous page
4 bytes next page
4 bytes overflow page (lower level index page)
1 byte compression level
1 byte 0x00
1 byte index level (0 = leaf)
452 bytes index bitmap, as in Jet3 but covering 3616 bytes
1 byte 0x00 (padding?)
3616 bytes (less free space) index records starting at offset 480 = 0x1e0

Compression: Index records after the first omit the first (compression
level) bytes.  The omitted bytes may span multiple components.  In an
extreme case the compressed records may be only one or two bytes long,
when a non-unique key is repeated many times mapping to rows on the
same page or nearby pages.

Index record format: basically the same as Jet3.

The overflow page is the last leaf page referred to in the "clean up
mode" comment.

*Intermediate index pages are observed to have a real record at the
beginning of the "free space."  This record points at the overflow
page and can be ignored as redundant.

Text index encoding:

Text data	Index encoding
'~'		0x2b, 0x0f (two bytes)
'_'		0x2b, 0x03 (two bytes)
'0'..'9'	0x36..0x48 (even numbers)
'A'		0x4a
'B'		0x4c
'C'..'J'	0x4d..0x5b (odd numbers)
'K'..'Q'	0x5c..0x68 (even numbers)
'R'..'X'	0x69..0x75 (odd numbers)
'Y'		0x76
'Z'		0x78

Encoding is case-insensitive.  Presumably 0x2b introduces a two byte
sequence.

Most text index entries end with 0x01, 0x00 rather than just a null byte.

Re: [mdb-dev] mdbtools and QT

[Brian B. <br...@br...>]

Using MDB Tools from a Qt applicatio should be no different than any othe=
r C/C++ app.  There are plenty of Qt programs out there that use glib-bas=
ed libraries. =20

The only special consideration would be calling "mdb_init()" before enter=
ing Qt's main loop (and mdb_exit() after), otherwise,  normal usage rules=
 apply.

Brian

----- Original Message -----
From: Rogerio Pereira <rog...@gm...>
Date: Fri, 27 Aug 2004 13:04:46 -0400
To: mdb...@li...
Subject: [mdb-dev] mdbtools and QT

> Hi!
>=20
> Where i can find any example of QT application using mdbtools api?
>=20
> Thanks for any answer,
>=20
> --=20
> Rog=E9rio Pereira Ara=FAjo
> Webmaster / Programador / Pesquisador
> C&S Computadores e Sistemas Ltda.
> www.cisnet.com.br
>=20
>=20
> -------------------------------------------------------
> This SF.Net email is sponsored by BEA Weblogic Workshop
> FREE Java Enterprise J2EE developer tools!
> Get your free copy of BEA WebLogic Workshop 8.1 today.
> http://ads.osdn.com/?ad_idP47&alloc_id=10808&op=3Dclick
> _______________________________________________
> mdbtools-dev mailing list
> mdb...@li...
> https://lists.sourceforge.net/lists/listinfo/mdbtools-dev

[mdb-dev] mdbtools and QT

[Rogerio P. <rog...@gm...>]

Hi!

Where i can find any example of QT application using mdbtools api?

Thanks for any answer,

--=20
Rog=E9rio Pereira Ara=FAjo
Webmaster / Programador / Pesquisador
C&S Computadores e Sistemas Ltda.
www.cisnet.com.br

Re: [mdb-dev] tests on ODBC and DBI perl module

[Jonathan D. <dix...@ly...>]

I have posted my first shot at the MdbSQL perl module on my website, http=
://dixonjon.tripod.com/MdbSQL.tgz

I believe this has everything needed for installation and operation of th=
e module.

Jon Dixon
dix...@ly...
http://dixonjon.tripod.com/


--=20
_______________________________________________
Find what you are looking for with the Lycos Yellow Pages
http://r.lycos.com/r/yp_emailfooter/http://yellowpages.lycos.com/default.=
asp?SRC=3Dlycos10

[mdb-dev] Northwind database - Orders Table bug

[Alexandre H. <ale...@fr...>]

Hi developers,

I was testing mdbtools with OOo mdb-driver and I found a bug in mdbtools
when loading Table Orders.  This bug also occurs with mdb-sql doing a
SELECT * FROM Orders and with gmdb2 that becomes very unstable (the
buttons disappear) after loading Orders 2 or 3 times. I verified there
was a loop which gets out of bounds. I placed a if, but you can rewrite
this loop. I hope this patch could help also for others databases.

Regards,
Alexandre Horst

Re: [mdb-dev] Compiling without gmdb

[Matt R. <mre...@te...>]

On Mon, 2004-08-16 at 19:48, br...@br... wrote:
> glib is not a gui library.  It is used throughout MDB Tools.  The
> configure script should detect libgtk, libgnome, and libglade
> automatically and compile in/out gmdb.  Glib2, however, is required
> for all the tools.
>=20
> Are you sure you have glib 2.x installed?  What does the config.log
> show?
>=20
> Brian

I had a few helpful follow-ups to this, but none that ultimately solved
the problem.  However, Brian (and others) were correct, glib wasn't
installed correctly.  However, I still don't know what I did in Cygwin
to fix this.  I installed the *entire* section marked Devel and that,
seemingly, solved the dependency issue (just marking glib-* for install
didn't solve the problem).

Thanks, all, for your help :)  Configure now runs just fine and I have a
working mdbtools.exe.
--=20
Matt Reynolds <mre...@te...>

Re: [mdb-dev] SQL problem

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

Is this database in Jet4 (Access 2000/2002)?  There are some known issues with
query results on Jet4 databases which I am currently working to track down.

 -- Jeff Smith


--- Jonathan Dixon <dix...@ly...> wrote:
> I'm having a little problem reading information from various tables in one of my MDB
> files (the main one I work with).
> 
> I started out having a problem with reading one of the tables in a database of mine
> using mdb-sql from the command line (or using any number of other means through
> mdbtools). Since there have been a number of recent patches posted to the CVS archive,
> I went ahead and downloaded those and recompiled mdbtools to see if that would fix the
> problem.
> 
> Well I can read that table now, but the others that worked before no longer work. A
> "Select * from Ranks" query (or whatever table I want to use) will pick up the columns
> for that table but will not retrieve any rows (which is what happened on the one table
> before).
> 
> I can read the same database through ADO and OpenOffice on my Windows machine and all
> of the info in the various tables is indeed there, so it doesn't appear to be the file
> itself.  Unfortunately the MDB file is fairly large and contains private information,
> so I cannot forward it along to assist in the debugging.  I am running Fedora Core 2 on
> an Intel machine. Is there something that changed in the recent revisions that might
> explain this behavior? Are there things I can check in the file to assist in the
> debugging? And most importantly, does anyone have any ideas for how I can actually read
> all the columns in my database?
> 
> Thanks for your help,
> 
> Jon Dixon
> dix...@ly...
> http://dixonjon.tripod.com/
> 


	
		
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
http://promotions.yahoo.com/new_mail 

[mdb-dev] SQL problem

[Jonathan D. <dix...@ly...>]

I'm having a little problem reading information from various tables in on=
e of my MDB files (the main one I work with).

I started out having a problem with reading one of the tables in a databa=
se of mine using mdb-sql from the command line (or using any number of ot=
her means through mdbtools). Since there have been a number of recent pat=
ches posted to the CVS archive, I went ahead and downloaded those and rec=
ompiled mdbtools to see if that would fix the problem.

Well I can read that table now, but the others that worked before no long=
er work. A "Select * from Ranks" query (or whatever table I want to use) =
will pick up the columns for that table but will not retrieve any rows (w=
hich is what happened on the one table before).

I can read the same database through ADO and OpenOffice on my Windows mac=
hine and all of the info in the various tables is indeed there, so it doe=
sn't appear to be the file itself.  Unfortunately the MDB file is fairly =
large and contains private information, so I cannot forward it along to a=
ssist in the debugging.  I am running Fedora Core 2 on an Intel machine. =
Is there something that changed in the recent revisions that might explai=
n this behavior? Are there things I can check in the file to assist in th=
e debugging? And most importantly, does anyone have any ideas for how I c=
an actually read all the columns in my database?

Thanks for your help,

Jon Dixon
dix...@ly...
http://dixonjon.tripod.com/


--=20
_______________________________________________
Find what you are looking for with the Lycos Yellow Pages
http://r.lycos.com/r/yp_emailfooter/http://yellowpages.lycos.com/default.=
asp?SRC=3Dlycos10

Re: [mdb-dev] mdbtools 0.6pre1 crash

[Alexandre H. <ale...@fr...>]

Hi All,

Jeff replied me in my personal address. I attached his answer and my
fields are displaying correct date/time values. Thanks Jeff! :)


On Sat, 2004-08-21 at 23:39, Jeff Smith wrote:=20
> I somehow forgot that simply typecasting from an integer to a
> floating-point value actually converts the value.  And Date/Time
> is stored as a double.  It should now be fixed.
>=20
>  -- Jeff


On Fri, 2004-08-20 at 18:09, Alexandre Horst wrote:
> Hi Jeff,
>=20
> I compiled the last CVS version of mdbtools and my database are not
> displaying correct Date/Time values. The table has corrupted data with
> the last version and right data with the version of 19-Aug. I think the
> error is in file.c, but I could not find. Could you look if this error
> occurs with you too?
>=20
> Best Regards
> Alexandre
>=20
>=20
[snip]

Best Regards
Alexandre

Re: [mdb-dev] SQL parsing

[<br...@br...>]

Access does it that way, but the SQL 99 standard is '' for string
literals and "" for identifiers.  I would personally like to keep the
SQL engine tracking the standard as close as possible.

I am not opposed to introducing [] to also mean identifier, as that is
supplemental and doesn't conflict with the standard.

On a side note, I think I'll finally get the time to merge some
patches this week.  The entire family (myself included) got the flu
over the past two weeks, and is just now recovering.

Brian

On Sat, 21 Aug 2004 22:11:19 -0700 (PDT), Jeff Smith wrote:

> 
> I will soon be taking a look at some of the SQL/ODBC issues raised
> recently, but first I
> want to take care of something a little more fundamental.
> 
> Currently, we parse SQL syntax something like this...
>   123 - numeric constant
>   xyz - identifier
>   'xyz' - string constant
>   "xyz" - identifier
> 
> Access does it more like this...
>   123 - numeric constant
>   xyz - identifier
>   'xyz' - string constant
>   "xyz" - string constant
>   [xyz] - identifier
> 
> I have a patch to change the parsing to the latter, but I am probing
> for any objections
> before I apply.  My personal feelings are we run the least risk by
> trying to match Access
> as closely as reasonably possible.
> 
>  -- Jeff Smith
> 
> 
> 		
> __________________________________
> Do you Yahoo!?
> Yahoo! Mail - 50x more storage than other providers!
> http://promotions.yahoo.com/new_mail
> 
> 
> -------------------------------------------------------
> SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank
Media
> 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
> Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
> http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
> _______________________________________________
> mdbtools-dev mailing list
> mdb...@li...
> https://lists.sourceforge.net/lists/listinfo/mdbtools-dev

[mdb-dev] SQL parsing

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

I will soon be taking a look at some of the SQL/ODBC issues raised recently, but first I
want to take care of something a little more fundamental.

Currently, we parse SQL syntax something like this...
  123 - numeric constant
  xyz - identifier
  'xyz' - string constant
  "xyz" - identifier

Access does it more like this...
  123 - numeric constant
  xyz - identifier
  'xyz' - string constant
  "xyz" - string constant
  [xyz] - identifier

I have a patch to change the parsing to the latter, but I am probing for any objections
before I apply.  My personal feelings are we run the least risk by trying to match Access
as closely as reasonably possible.

 -- Jeff Smith


		
__________________________________
Do you Yahoo!?
Yahoo! Mail - 50x more storage than other providers!
http://promotions.yahoo.com/new_mail

[mdb-dev] test mdbtools cvs version 20040821

[Filippo B. <fil...@io...>]

Report of some tests.

Compilation and installation (slackware 10) end with no problem. 

I've preparted 2 files with the same tables: 
db0.mdb made with Access 2000 and 
db0acc97.mdb made with Access 97. 

Although with mdbtools ver 0.5 the various mdb-programs worked well,
with ver 0.6 there are some problems with jet4 files:

$ mdb-tables  db0acc97.mdb  test00
test00 test1 test0 test

$ mdb-tables  db0.mdb  test00
test test0

2 tables are not found. 

Also other programs fail.


Test with ODBC are not been carried out because a connection cannot be established: 

isql -v testmdb
Can't alloc filename
Can't alloc filename
Unable to locate database /tmp/out.db
[ISQL]ERROR: Could not SQLConnect


Test with sdb (OOo database driver) has failed.
Mdbtools code I've tried seems to have been fixed according to the patch proposed here:
http://dba.openoffice.org/drivers/mdb/diff-mdbtools.diff

but probably something must be set also in the binary driver.

Best regards.
F 

Re: [mdb-dev] mdbtools 0.6pre1 crash

[Alexandre H. <ale...@fr...>]

Hi Jeff,

I compiled the last CVS version of mdbtools and my database are not
displaying correct Date/Time values. The table has corrupted data with
the last version and right data with the version of 19-Aug. I think the
error is in file.c, but I could not find. Could you look if this error
occurs with you too?

Best Regards
Alexandre


On Fri, 2004-08-20 at 01:32, Jeff Smith wrote:=20
> I have not investigated the areas you are referring to, but mdb-export
> is working for me on this file now.
>=20
> The first problem was in the function that determines which pages are
> used by a large table.  The fix for this is in CVS.
>=20
> The other part is with exporting fields marked as type OLE.  Access's
> export seems to treat them as empty fields.  Changing mdb-export to do
> the same and it works like a champ.  I have not determined if this is
> the 'right' thing to do.  To test it yourself, change line 172 of
> src/util/mdb-export.c to
>=20
>    bound_values[j][0] =3D '\0';
>=20
>  -- Jeff Smith
>=20
>=20
> --- John Carr <jf...@MI...> wrote:
> >=20
> > I noticed a difference between the file format of RoadInventory.mdb
> > and the format documented in HACKING, which in this respect appears
> > to be the same as is expected by index.c.
> >=20
> > The per-index block that is listed as 27 bytes for Jet4 tables is
> > actually 28 bytes long.  There is an extra zero byte between these
> > two values:
> >=20
> > | ???? | 4 bytes | index_num2  | Number of the index (repeat)          =
   |
> > | 0xFF | 4 bytes | ???         |                                       =
   |
> >=20
> > I also believe that the "unknown" value a few lines, the middle of the
> > three I quote below is actually a row/data page pointer.  What it
> > points to, I have not determined, but the values appear to point at
> > distinct and otherwise unused rows in a data page associated with the
> > table.
> >=20
> > | ???? | 1 byte  | col_order   | 0x01 =3D  ascendency order            =
     |
> > +----------------------------------------------------------------------=
---+
> > | ???? | 4 bytes | unknown     |                                       =
   |
> > | ???? | 4 bytes | first_dp    | Data pointer of the index page        =
   |
> >=20
> >=20
> > > I tested the file on my machine (IA-32 running Linux) and it core dum=
ped
> > > here too.  I am looking into it, and I will let you know when I know =
more.
> > >=20
> > >  -- Jeff Smith
> > >=20
> > >=20
> > > --- John Carr <jf...@MI...> wrote:
> > > >=20
> > > > I built mdbtools 0.6pre1 with the Sun C compiler in 64 bit mode on =
a
> > > > SPARC running Solaris 8.  I have a file which makes mdb-export cras=
h.
> > > > Fetch and unpack <http://www.mhd.state.ma.us/planning/RoadInv_GDB.z=
ip>
> > > > (unpacks to over 300 MB).  Run
> > > > % mdb-export RoadInventory.mdb RoadInventory
> > > > mdb-export spews a series of garbage lines then dumps core.
> > > >=20
> > > > The proximate cause of the crash is an array overflow of the
> > > > /text/ array in mdb_col_to_string because argument /size/ exceeds
> > > > MDB_BIND_SIZE, but I think the program went wrong long before that.
> >=20
>=20
>=20
>=20
> 	=09
> __________________________________
> Do you Yahoo!?
> New and Improved Yahoo! Mail - Send 10MB messages!
> http://promotions.yahoo.com/new_mail
>=20
>=20
> -------------------------------------------------------
> SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
> 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
> Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
> http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
> _______________________________________________
> mdbtools-dev mailing list
> mdb...@li...
> https://lists.sourceforge.net/lists/listinfo/mdbtools-dev
>=20

Re: [mdb-dev] mdbtools 0.6pre1 crash

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

Oh, yeah, I remember this now.  I fixed this in CVS about two months ago:

  http://cvs.sourceforge.net/viewcvs.py/mdbtools/mdbtools/HACKING?r1=1.16&r2=1.17

 -- Jeff Smith


--- John Carr <jf...@MI...> wrote:
> 
> I noticed a difference between the file format of RoadInventory.mdb
> and the format documented in HACKING, which in this respect appears
> to be the same as is expected by index.c.
> 
> The per-index block that is listed as 27 bytes for Jet4 tables is
> actually 28 bytes long.  There is an extra zero byte between these
> two values:
> 
> | ???? | 4 bytes | index_num2  | Number of the index (repeat)             |
> | 0xFF | 4 bytes | ???         |                                          |



		
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!
http://promotions.yahoo.com/new_mail 

Re: [mdb-dev] mdbtools 0.6pre1 crash

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

I have not investigated the areas you are referring to, but mdb-export
is working for me on this file now.

The first problem was in the function that determines which pages are
used by a large table.  The fix for this is in CVS.

The other part is with exporting fields marked as type OLE.  Access's
export seems to treat them as empty fields.  Changing mdb-export to do
the same and it works like a champ.  I have not determined if this is
the 'right' thing to do.  To test it yourself, change line 172 of
src/util/mdb-export.c to

   bound_values[j][0] = '\0';

 -- Jeff Smith


--- John Carr <jf...@MI...> wrote:
> 
> I noticed a difference between the file format of RoadInventory.mdb
> and the format documented in HACKING, which in this respect appears
> to be the same as is expected by index.c.
> 
> The per-index block that is listed as 27 bytes for Jet4 tables is
> actually 28 bytes long.  There is an extra zero byte between these
> two values:
> 
> | ???? | 4 bytes | index_num2  | Number of the index (repeat)             |
> | 0xFF | 4 bytes | ???         |                                          |
> 
> I also believe that the "unknown" value a few lines, the middle of the
> three I quote below is actually a row/data page pointer.  What it
> points to, I have not determined, but the values appear to point at
> distinct and otherwise unused rows in a data page associated with the
> table.
> 
> | ???? | 1 byte  | col_order   | 0x01 =  ascendency order                 |
> +-------------------------------------------------------------------------+
> | ???? | 4 bytes | unknown     |                                          |
> | ???? | 4 bytes | first_dp    | Data pointer of the index page           |
> 
> 
> > I tested the file on my machine (IA-32 running Linux) and it core dumped
> > here too.  I am looking into it, and I will let you know when I know more.
> > 
> >  -- Jeff Smith
> > 
> > 
> > --- John Carr <jf...@MI...> wrote:
> > > 
> > > I built mdbtools 0.6pre1 with the Sun C compiler in 64 bit mode on a
> > > SPARC running Solaris 8.  I have a file which makes mdb-export crash.
> > > Fetch and unpack <http://www.mhd.state.ma.us/planning/RoadInv_GDB.zip>
> > > (unpacks to over 300 MB).  Run
> > > % mdb-export RoadInventory.mdb RoadInventory
> > > mdb-export spews a series of garbage lines then dumps core.
> > > 
> > > The proximate cause of the crash is an array overflow of the
> > > /text/ array in mdb_col_to_string because argument /size/ exceeds
> > > MDB_BIND_SIZE, but I think the program went wrong long before that.
> 



		
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!
http://promotions.yahoo.com/new_mail 

Re: [mdb-dev] mdbtools 0.6pre1 crash

[John C. <jf...@MI...>]

I noticed a difference between the file format of RoadInventory.mdb
and the format documented in HACKING, which in this respect appears
to be the same as is expected by index.c.

The per-index block that is listed as 27 bytes for Jet4 tables is
actually 28 bytes long.  There is an extra zero byte between these
two values:

| ???? | 4 bytes | index_num2  | Number of the index (repeat)             |
| 0xFF | 4 bytes | ???         |                                          |

I also believe that the "unknown" value a few lines, the middle of the
three I quote below is actually a row/data page pointer.  What it
points to, I have not determined, but the values appear to point at
distinct and otherwise unused rows in a data page associated with the
table.

| ???? | 1 byte  | col_order   | 0x01 =  ascendency order                 |
+-------------------------------------------------------------------------+
| ???? | 4 bytes | unknown     |                                          |
| ???? | 4 bytes | first_dp    | Data pointer of the index page           |


> I tested the file on my machine (IA-32 running Linux) and it core dumped
> here too.  I am looking into it, and I will let you know when I know more.
> 
>  -- Jeff Smith
> 
> 
> --- John Carr <jf...@MI...> wrote:
> > 
> > I built mdbtools 0.6pre1 with the Sun C compiler in 64 bit mode on a
> > SPARC running Solaris 8.  I have a file which makes mdb-export crash.
> > Fetch and unpack <http://www.mhd.state.ma.us/planning/RoadInv_GDB.zip>
> > (unpacks to over 300 MB).  Run
> > % mdb-export RoadInventory.mdb RoadInventory
> > mdb-export spews a series of garbage lines then dumps core.
> > 
> > The proximate cause of the crash is an array overflow of the
> > /text/ array in mdb_col_to_string because argument /size/ exceeds
> > MDB_BIND_SIZE, but I think the program went wrong long before that.

Re: [mdb-dev] Compiling without gmdb

[Michael W. <mw...@ic...>]

On Wed, Aug 18, 2004 at 01:50:35PM -0700, Matt Reynolds wrote:
[snip]
> I get this error :
> checking for GLIB - version >= 2.0.0... no
> *** Could not run GLIB test program, checking why...
> *** The test program failed to compile or link. See the file config.log
> for the
> *** exact error that occured. This usually means GLIB is incorrectly
> installed.
[snip]
> configure:8396: checking for GLIB - version >= 2.0.0
> configure:8512: gcc -o conftest.exe -g -O2 -DSQL -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include     conftest.c -lglib-2.0 -lintl -liconv    >&5
> /usr/lib/gcc-lib/i686-pc-cygwin/3.3.3/../../../../i686-pc-cygwin/bin/ld: cannot find -liconv
> collect2: ld returned 1 exit status
[snip]

I think the problem is with iconv, not glib.

-- 
Michael Wood <mw...@ic...>

Re: [mdb-dev] Compiling without gmdb

[Matt R. <mre...@te...>]

On Mon, 2004-08-16 at 19:48, br...@br... wrote:
> glib is not a gui library.  It is used throughout MDB Tools.  The
> configure script should detect libgtk, libgnome, and libglade
> automatically and compile in/out gmdb.  Glib2, however, is required
> for all the tools.
> 
> Are you sure you have glib 2.x installed?  What does the config.log
> show?

My sincerest apologies.  I totally blew a gasket and kept reading glib
as gtk.  So please ignore my inane rambling about the GUI.

Also, I seemed to have totally blown another gasket.  The error I was
recieving had little to do with glib, but to do with pkg-config.

However, after recovering from these delusions, I have discovered an
error that I don't understand from the data provided.

I get this error :
checking for GLIB - version >= 2.0.0... no
*** Could not run GLIB test program, checking why...
*** The test program failed to compile or link. See the file config.log
for the
*** exact error that occured. This usually means GLIB is incorrectly
installed.

glib 2.0 is required by MDB Tools.
It can be downloaded at www.gtk.org.

The log is also attached.  Unfortunately, I know very little about
autoconf, otherwise I'd try that route.

Thanks, and sorry about the earlier confusion.
-- 
Matt Reynolds <mre...@te...>

Re: [mdb-dev] tests on ODBC and DBI perl module

[Jonathan D. <dix...@ly...>]

I also didn't have much success with the ODBC interface, so I am developi=
ng a Perl XSUB module (similar to, and drawing inspiration from, the mdbt=
ools module) to handle SQL queries through the libmdbsql library. This ma=
de especial sense given that my needs were fairly simple so I really didn=
't need to deal with the extra overhead that ODBC would entail.

My module (MdbSQL) is at this point still quite early in its development,=
 although on the couple of examples I have it seems to work.  The results=
 come as a hash with the requested column names as keys and can either be=
 popped off one hash reference at a time or all at once as an array of ha=
shes.  As an added bonus, I have implemented a basic "order by" parser/ro=
utine so that the query can produce sorted outputs (it made my overall ap=
plication easier).  I have ideas on how to implement statements of the fo=
rm "select table1.column3, table2.column2 from table1, table2 where xxxxx=
 order by table1.column4 desc" but haven't had the time to actually try t=
hese out.  So far my application hasn't really needed that, so it isn't a=
 priority. I have also been considering how to make the module a little m=
ore robust in handling bad queries, but haven't gotten around to implemen=
ting these either.

If you are interested in trying these out, I am certainly willing to shar=
e them with you.  It will be about a week before I have a chance to wrap =
things up into a distributable package (ie add some rudimentary documenta=
tion, clean up some areas, get the tests working better, etc), but after =
that I could make them available if you would like.

Jon Dixon
dix...@ly...
http://dixonjon.tripod.com/


--=20
_______________________________________________
Find what you are looking for with the Lycos Yellow Pages
http://r.lycos.com/r/yp_emailfooter/http://yellowpages.lycos.com/default.=
asp?SRC=3Dlycos10

[mdb-dev] tests on ODBC and DBI perl module

[Filippo B. <fil...@io...>]

Hi,

i'm a newbie of this list. 

I'm a scarse perl programer and i've tried mdb-odbc with perl DBD::ODBC
with poor results. 

I've done some tests that suggest that it's better to leave odbc alone
and try to develope drivers and modules, even thought it's an harder way
to
go.

#####################
Report of tests 

I've created an mdb file with Ms-Access named 'db0.mdb' with some
tables:

This is schema of test00 table as presented by mdb-schema:

 	ID                      Long Integer (4),
        col0                    Text (100),
        col1                    Double (8),
        col2                    Boolean,
        col3                    DateTime (Short) (8)


This is the content of table test00 as presented by mdb-export 

$ mdb-export /tmp/db0.mdb test00
ID,col0,col1,col2,col3
"1","prova1",18234.293400,1,"06/19/04 00:00:00"
"2","prova2",1234.234240,0,"04/20/04 00:00:00"
"3","prova3",23423.234430,1,"12/31/03 00:00:00"

and by mdb-sql

$ mdb-sql /tmp/db0.mdb
1 => select * from test00
2 => go

+-------+--------------------------------------------------------------
--------------------------------------+----------+-+-------------------
-+
|ID     |col0                                                           
|                                    |col1      |c|col3                |
+-------+--------------------------------------------------------------
--------------------------------------+----------+-+-------------------
-+
|1      |prova1                                                         
|                                    |18234.2934|1|06/19/04 00:00:00   |
|2      |prova2                                                         
|                                    |1234.23424|0|04/20/04 00:00:00   |
|3      |prova3                                                         
|                                    |23423.2344|1|12/31/03 00:00:00   |
+-------+--------------------------------------------------------------
--------------------------------------+----------+-+-------------------
-+
3 Rows retrieved

and now let's try perl with the preliminary module prepared by  Kyle R.
Burton
(http://www.neverlight.com/~mortis/mdbtools/)

This is the test script adapted from synopsis
-------- mytest.pl --------
use strict;
      use warnings;
      use Mdbtools;
      my $mdb = Mdbtools->new('/tmp/db0.mdb');
      print "tables: \n",join("\n  ",$mdb->get_table_names),"\n";

      print "all tables: \n",join("\n 
",$mdb->get_all_table_names),"\n";
       my @entire_table = $mdb->get_all_records('test00');

       $mdb->open_table('test00');
       while( my @rec = $mdb->fetch_record ) {
         print "record: @rec\n";
       }
      $mdb->close_table('test00');
--------------------------------------

and this is the output:

$ perl mytest.pl
------------
tables:
test
  test0
  test1
  test00
all tables:
MSysObjects
  MSysACEs
  MSysQueries
  MSysRelationships
  MSysAccessObjects
  test
  test0
  test1
  test00
record: 1 prova1 18234.293400 1 19/06/2004 00:00:00
record: 2 prova2 1234.234240 0 20/04/2004 00:00:00
record: 3 prova3 23423.234430 1 31/12/2003 00:00:00
-------------

as you can see till now everything seems to go fairly well. 

########################################
Now let's watch at odbc.

isql -v  testmdb
+---------------------------------------+
| Connected!                            |
|                                       |
| sql-statement                         |
| help [tablename]                      |
| quit                                  |
|                                       |
+---------------------------------------+
SQL> select * from test00
+---------+------------------------------------------------------------
-----------------------------------------+-----------+-----------+-----
------+
| ID      | col0                                                        
|                                        | col1      | col2      | col3 
|                                        |     |
+---------+------------------------------------------------------------
-----------------------------------------+-----------+-----------+-----
------+
Segmentation fault



also with a very simple table with just 1 text field and 1 record the
result is bad: 

+-----------+
|           |
+-----------+
[24000][unixODBC][Driver Manager]Invalid cursor state
+-----------+
1 rows affected

(it keeps repeating the result and never stops)


Perl DBD::ODBC goes badly too:

------- testmdbodbc.pl --------
use DBI;

my $source = 'testmdb' ;

my    $dsn = "DBI:ODBC:$source" ;
my    $dbh = DBI->connect($dsn );

###  it fails without this 
  $dbh->{'LongTruncOk'} = 1 ;

$query = " select * from test00" ;

$sth = $dbh->prepare("$query") ;
$sth->execute() ;

     my @data ;
     while( @data = $sth->fetchrow_array() )
    {
    foreach $x (@data) { print "$x\t" ; }
    print "\n" ;
    }

 $sth->finish;
 $dbh->disconnect ;

--------------------------------

$ perl testmdbodbc.pl

1       prova1  1               1
2       prova2  1               2
3       prova3  2               3
Segmentation fault


unixODBC installation has been tested with myodbc and mysql database
with good results, so i don't think the problem is there.


##############
Some tests also with OpenOffice 

Using Data Sources ODBC driver, connection seems to work but no tables
are displayed. 


Then I've used the sdb-driver found on openoffice dba web site:

http://dba.openoffice.org/drivers/mdb/

uninstalled the default version of mdbtools and installed the patched
one.

then followed the installation instructions of sdb driver. 

In this case tables are displayed and is to possible to retrive data
from table test00, import them in a spreadsheet and so on.

I've also repeated the above tests with the patched version of mdbtools
with the same results. 




 

Re: [mdb-dev] Compiling without gmdb

[<br...@br...>]

glib is not a gui library.  It is used throughout MDB Tools.  The
configure script should detect libgtk, libgnome, and libglade
automatically and compile in/out gmdb.  Glib2, however, is required
for all the tools.

Are you sure you have glib 2.x installed?  What does the config.log
show?

Brian

On Mon, 16 Aug 2004 16:49:04 -0700, "Matt Reynolds" wrote:

> 
> I'm trying to compile mdbtools under Cygwin on XP.  Configure is
> telling
> me that I don't have glib installed (I think I installed the glib-dev
> version, but have no CLI way of confirming this easily).
> 
> As I don't intend to use the GUI anyway, is there a way to disable
> trying to build the GUI and just give me the CLI version of the
tool? 
> I
> tried --disable-glibtest and --without-glibtest for configure, but
> those
> didn't disable the check.
> 
> Any ideas?  I'm not that savvy with configure (and unfortunately, not
> savvy with cygwin either).  This worked great on my Linux box, but
> Windows is giving me problems.
> -- 
> Matt Reynolds <mre...@te...>

[mdb-dev] Compiling without gmdb

[Matt R. <mre...@te...>]

I'm trying to compile mdbtools under Cygwin on XP.  Configure is telling
me that I don't have glib installed (I think I installed the glib-dev
version, but have no CLI way of confirming this easily).

As I don't intend to use the GUI anyway, is there a way to disable
trying to build the GUI and just give me the CLI version of the tool?  I
tried --disable-glibtest and --without-glibtest for configure, but those
didn't disable the check.

Any ideas?  I'm not that savvy with configure (and unfortunately, not
savvy with cygwin either).  This worked great on my Linux box, but
Windows is giving me problems.
--=20
Matt Reynolds <mre...@te...>

Re: [mdb-dev] mdbtools 0.6pre1 crash

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

I tested the file on my machine (IA-32 running Linux) and it core dumped
here too.  I am looking into it, and I will let you know when I know more.

 -- Jeff Smith


--- John Carr <jf...@MI...> wrote:
> 
> I built mdbtools 0.6pre1 with the Sun C compiler in 64 bit mode on a
> SPARC running Solaris 8.  I have a file which makes mdb-export crash.
> Fetch and unpack <http://www.mhd.state.ma.us/planning/RoadInv_GDB.zip>
> (unpacks to over 300 MB).  Run
> % mdb-export RoadInventory.mdb RoadInventory
> mdb-export spews a series of garbage lines then dumps core.
> 
> The proximate cause of the crash is an array overflow of the
> /text/ array in mdb_col_to_string because argument /size/ exceeds
> MDB_BIND_SIZE, but I think the program went wrong long before that.



		
__________________________________
Do you Yahoo!?
Yahoo! Mail - 50x more storage than other providers!
http://promotions.yahoo.com/new_mail