mdbtools-dev

Re: [mdb-dev] mdb-export and embedded \t,\r,\n and quotes

[Kyle R. B. <mo...@vo...>]

Whoops!  I forgot to attach the patch files.  Please excuse the earlier
email.

They should be attached to this one.

Kyle


On Wed, Aug 06, 2003 at 05:40:22PM -0400, Kyle R. Burton wrote:
> Hello again.
> 
> In using mdb-export, we've run into a few snags with data that contains
> embedded newlines, carriage returns, tabs and quotes.  There are
> options for mdb-export to supress quoting, and to specify an alternate
> delimiter.  Unfortunately these options weren't enough to handle the
> data we were trying to dump from our MDB files.
> 
> I modified mdb-export and added a few new options:
> 
>   -q <string>    specify a column quoting string (defaults to ")
>   -e <string>    specify an escape string that will be substituted
>                  for a double quote in data (defaults to a pair of
>                  double quotes)
>   -d <delimiter> specify a column delimiter (default is a comma)
>   -R <eol>       specify a record delimiter (default is a single newline)
> 
> I also made some changes to the behavior of mdb-export based on
> these options.  The changes preserve the original behavior of 
> mdb-export with the default values for the new options.
> 
>   - the code now looks for quote_string instead of a hard-coded double
>     quote - emitting escape_string in place of quote_string.  This
>     means using strstr() instead of single character comparisons.
>   - the header row is now quoted unless -Q is specified.  We were seeing
>     column names with all kinds of special characters in them - commas,
>     spaces, etc.
>   - escape_string (defaults to ", overrideable via a command line switch)
>     is emitted in place of any quote_string values that column data 
>     contains.  It is not emitted before the quote_string, it is emitted
>     instead of the quote_string, so a double quote can be replaced
>     entirely by another string.
> 
> For our data processing, we composed a more complex command line:
> 
>   [mortis@magenta]$ mdb-export -q "'" -e "&quot;" -R "
> ***RECORD SEPARATOR***
> " -d " ||delimiter|| " ~/CREDITS_IMPORT.mdb ALL_CREDS |& less
> 
> The record seperator we specified has embedded newlines in it:
> 
>    "\n***RECORD SEPARATOR***\n"
> 
> This way in the Perl code that we're using to wrap the output of mdb-export,
> we can set the input record seperator ($/) to that record delimiter.  Doing
> that makes delimiting the records very easy.  The pre-existing escaping
> features, combined with the ability to specify the quote character and 
> the software looking for that character makes parsing the fields very easy 
> as well.  Even in the presence of all the embedded meta characters.
> 
> 
> I've attached two patches, mdbtools-combined.patch includes the changes
> from the perspective of 0.5rc2 for the whole archive, including the
> patch sent by David Mansfield <mdb...@dm...>.
> 
> The second patch, mdb-export.patch2, is just my changes to mdb-export 
> (assuming David Mansfield's patch as a baseline).
> 
> 
> 
> 
> Thanks,
> Kyle
> 
> 
> 
> -- 
> 
> ------------------------------------------------------------------------------
> Wisdom and Compassion are inseparable.
>         -- Christmas Humphreys
> mo...@vo...                            http://www.voicenet.com/~mortis
> ------------------------------------------------------------------------------
> 
> 
> -------------------------------------------------------
> This SF.Net email sponsored by: Free pre-built ASP.NET sites including
> Data Reports, E-commerce, Portals, and Forums are available now.
> Download today and enter to win an XBOX or Visual Studio .NET.
> http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
> _______________________________________________
> mdbtools-dev mailing list
> mdb...@li...
> https://lists.sourceforge.net/lists/listinfo/mdbtools-dev

-- 

------------------------------------------------------------------------------
Wisdom and Compassion are inseparable.
        -- Christmas Humphreys
mo...@vo...                            http://www.voicenet.com/~mortis
------------------------------------------------------------------------------

Re: [mdb-dev] mdb-sql: Readline Completion Support

[Mark K. <kil...@nb...>]

Michael Wood wrote:
> Hi
> 
> Since I am basically just a lurker on this list, feel free to ignore
> these comments:

Me too.  I want to use the MDB tools to look at a db under my Linux box 
(I *hate* rebooting into Windows!)

> 2.)  Gratuitous whitespace changes get in the way of what your patch is
> doing.  The reviewer has to waste time looking through the whitespace
> changes to see if you made any other changes in that section besides
> just the whitespace changes.

In most diff programs, you can ignore whitespace changes.  Take the GNU 
diff on my system:

-b     Ignore changes in amount of white space.
-B     Ignore changes that just insert or delete blank lines.

White space changes are actually a good thing, if they improve 
readability, so I wouldn't poo-poo them entirely...

You can add these options to your .cvsrc if you are using cvs.

Just a hint...

MK
-- 
"An expert is a man who has made all the mistakes which can be made,
in a narrow field."   - Niels Bohr
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Mark Kilfoil                                   <kil...@nb...>
  Software Designer/Developer, Radio Host, Gamer, Curmudgeon, Oddball
     From the FINE mega-city of Fredericton, New Brunswick, Canada
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

[mdb-dev] mdb-export and embedded \t,\r,\n and quotes

[Kyle R. B. <mo...@vo...>]

Hello again.

In using mdb-export, we've run into a few snags with data that contains
embedded newlines, carriage returns, tabs and quotes.  There are
options for mdb-export to supress quoting, and to specify an alternate
delimiter.  Unfortunately these options weren't enough to handle the
data we were trying to dump from our MDB files.

I modified mdb-export and added a few new options:

  -q <string>    specify a column quoting string (defaults to ")
  -e <string>    specify an escape string that will be substituted
                 for a double quote in data (defaults to a pair of
                 double quotes)
  -d <delimiter> specify a column delimiter (default is a comma)
  -R <eol>       specify a record delimiter (default is a single newline)

I also made some changes to the behavior of mdb-export based on
these options.  The changes preserve the original behavior of 
mdb-export with the default values for the new options.

  - the code now looks for quote_string instead of a hard-coded double
    quote - emitting escape_string in place of quote_string.  This
    means using strstr() instead of single character comparisons.
  - the header row is now quoted unless -Q is specified.  We were seeing
    column names with all kinds of special characters in them - commas,
    spaces, etc.
  - escape_string (defaults to ", overrideable via a command line switch)
    is emitted in place of any quote_string values that column data 
    contains.  It is not emitted before the quote_string, it is emitted
    instead of the quote_string, so a double quote can be replaced
    entirely by another string.

For our data processing, we composed a more complex command line:

  [mortis@magenta]$ mdb-export -q "'" -e "&quot;" -R "
***RECORD SEPARATOR***
" -d " ||delimiter|| " ~/CREDITS_IMPORT.mdb ALL_CREDS |& less

The record seperator we specified has embedded newlines in it:

   "\n***RECORD SEPARATOR***\n"

This way in the Perl code that we're using to wrap the output of mdb-export,
we can set the input record seperator ($/) to that record delimiter.  Doing
that makes delimiting the records very easy.  The pre-existing escaping
features, combined with the ability to specify the quote character and 
the software looking for that character makes parsing the fields very easy 
as well.  Even in the presence of all the embedded meta characters.


I've attached two patches, mdbtools-combined.patch includes the changes
from the perspective of 0.5rc2 for the whole archive, including the
patch sent by David Mansfield <mdb...@dm...>.

The second patch, mdb-export.patch2, is just my changes to mdb-export 
(assuming David Mansfield's patch as a baseline).




Thanks,
Kyle



-- 

------------------------------------------------------------------------------
Wisdom and Compassion are inseparable.
        -- Christmas Humphreys
mo...@vo...                            http://www.voicenet.com/~mortis
------------------------------------------------------------------------------

Re: [mdb-dev] Perl Answer and another Question about spaces in column names

[Kyle R. B. <mo...@vo...>]

> A few days back I posted to ask how you could use mdb-tools command line 
> utilities from within perl.  A few folks replied but I didn't really follow 
> alot of it, Im not that familar with perl or mdb-tools.  Just bang the 
> following snippit of code into your perl script:
> 
> 
> open AFILE, "|mdb-sql db1.mdb>fred.txt";
> 
> print AFILE <<"ENDOFQUERY" ;
> 
> list tables
> go
> quit
> 
> ENDOFQUERY
> 
> close(AFILE);
> 
> the lines btw print AFILE <<"ENDOFQUERY" ; and ENDOFQUERY are just as you would 
> enter them at the command line.  So I hope this helps someone in future.  I am 
> guessing these emails are stored somewhere online.
> 
> I do have another question.  I want to select all the contents of two columns 
> from a table.  But at the moment I can't select anything from the table because 
> the table name has an underscore in it!  Anybody know the correct way to format 
> such a query?

You can try enclosing it in single or double quotes:

  select 'col_1','col2' from table
  go

  select "col_1","col2' from table
  go

The patch that was sent in for sql/lexer.l fixes the underscore issue - it
makes more characters valid in table and column names, and in strings,
specifically the patch allows any alphanumerics and the underscore in
a bare (un-quoted) name, and additionaly allows spaces in a double quoted
string.  MS Access allows a surprising variety of characters in table
names, so these additions alone are not enough to cover all the 
possibilities.  I've seen table or column namess with the following
characters in them: ~@#$%&*()-_=+,<>/\{}

Hope this helps.

Kyle

  

-- 

------------------------------------------------------------------------------
Wisdom and Compassion are inseparable.
        -- Christmas Humphreys
mo...@vo...                            http://www.voicenet.com/~mortis
------------------------------------------------------------------------------

[mdb-dev] Sorry I forgot..

[RI D. <s02...@sm...>]

In the previous post, the results of the query are printed to a file that is 
created called fred.txt

:-)

[mdb-dev] Perl Answer and another Question about spaces in column names

[RI D. <s02...@sm...>]

Hello.

A few days back I posted to ask how you could use mdb-tools command line 
utilities from within perl.  A few folks replied but I didn't really follow 
alot of it, Im not that familar with perl or mdb-tools.  Just bang the 
following snippit of code into your perl script:


open AFILE, "|mdb-sql db1.mdb>fred.txt";

print AFILE <<"ENDOFQUERY" ;

list tables
go
quit

ENDOFQUERY

close(AFILE);

the lines btw print AFILE <<"ENDOFQUERY" ; and ENDOFQUERY are just as you would 
enter them at the command line.  So I hope this helps someone in future.  I am 
guessing these emails are stored somewhere online.

I do have another question.  I want to select all the contents of two columns 
from a table.  But at the moment I can't select anything from the table because 
the table name has an underscore in it!  Anybody know the correct way to format 
such a query?

Kind Regards,

Rob

[mdb-dev] Re: MDB-Tools and Perl

[Celeste S. B. <csb...@ci...>]

It sure would be nice if someone wrote a module and posted it to CPAN (hint,
hint)

Celeste Suliin Burris
Systems Administrator
Tacoma Economic Development Dept.
csb...@ci...


> Date: Mon, 4 Aug 2003 09:17:55 -0400
> From: "Kyle R. Burton" <mo...@vo...>
> To: mdb...@li...
> Subject: Re: [mdb-dev] MDB-Tools and Perl
> Reply-To: "Kyle R. Burton" <mo...@vo...>
> 
>> I am curious as to the ways in which one can interact with mdb-tools from
>> within a perl script?  I am not a strong programmer.  I can use the system
>> command from perl to start the command line utilities but can not pass it the
>> required information.  Does anyone have much experience of working with both
>> MDB tools and perl?
> 
> We have used MDB tools from Perl to list the tables in an MDB (using
> mdb-tables), and get all the records from a table (using mdb-export).
> 
> We either used backticks or open to read from those commands.  A direct call
> to the C functions (libmdb) would probably be a better long teram solution
> (DBD::mdbtools would be even better).
> 
> Pseudo code for we're using looks like:
> 
> # returns an array of table names
> sub list_tables
> {
>   my($fileName) = @_;
>   my $cmd = "mdb-tables $fileName";
>   my $output = `$cmd`;
>   if( 0 != ($? >> 8) ) {
>       die "Error obtaining tables list [$cmd]: $output : \$!=>$! : \$?=>$?";
>   }
>   my @lines = split(/[\s\r\n]+/,$output);
>   return @lines;
> }
> 
> # returns an array of arrayrefs (array of records)
> sub get_records
> {
>   my($fileName,$tableName) = @_;
>   my $cmd = "mdb-export -d'\t' -Q $fileName '$tableName' |;
>   my $fh;
>   unless( open( $fh, $cmd ) ) {
>       die "Error opening mdb read handle: $! : cmd: '$cmd'";
>   }
>   my @lines = <$fh>;
>   close $fh;
>   my @records;
>   foreach my $line ( @lines ) {
>       my @fields = split('\t',$line);
>       $fields[-1] =~ s/[\r\n]+//;
>       push @records, \@fields;
>   }
>   return @records;
> }
> 
> 
> 
> -- 
> 
> ------------------------------------------------------------------------------
> Wisdom and Compassion are inseparable.
>       -- Christmas Humphreys
> mo...@vo...                            http://www.voicenet.com/~mortis
> ------------------------------------------------------------------------------

Re: [mdb-dev] Compacat & Repair Database Issues

[David M. <mdb...@dm...>]

On Tue, 5 Aug 2003, Kyle R. Burton wrote:

> Hello,
> 
> I just discovered an issue with mdb-export (it might be more pervasive
> in the library, I haven't dug too much further into the issue).
> 
> I've created an mdb file, then edited it by changing the column names,
> or editing the cell data (not adding new rows, just editing existing data).  
> After these edits, mdb-export prints an empty field for the edited cells.  
> If, in MS Access, I run
> 
>   Tools->Database Utilities->Compact and Repair Database...
> 
> mdb-export then shows the correct cell values.
> 
> I didn't know if this was a known issue, I searched the mdbtools-dev list
> archive on sourceforge and didn't come up with any hits for 'compact',
> and there was nothing that I could see in the FAQ.
> 
> I also didn't know if there was something in the file's structure/format 
> that could point to where the new data is (I'm not at all fmailliar with 
> the internal structures of the mdb file format - I've never even looked
> at it).
> 

I've attached a patch to the 0.5rc2 release of mdbtools that fixes a large
handful of data handling problems.  Could you try the attached patch 
(apply and rebuild your programs)? 

If you try this, let me know if it does/doesn't help you out.

David

-- 
/==============================\
| David Mansfield              |
| mdb...@db...       |
\==============================/

[mdb-dev] Compacat & Repair Database Issues

[Kyle R. B. <mo...@vo...>]

Hello,

I just discovered an issue with mdb-export (it might be more pervasive
in the library, I haven't dug too much further into the issue).

I've created an mdb file, then edited it by changing the column names,
or editing the cell data (not adding new rows, just editing existing data).  
After these edits, mdb-export prints an empty field for the edited cells.  
If, in MS Access, I run

  Tools->Database Utilities->Compact and Repair Database...

mdb-export then shows the correct cell values.

I didn't know if this was a known issue, I searched the mdbtools-dev list
archive on sourceforge and didn't come up with any hits for 'compact',
and there was nothing that I could see in the FAQ.

I also didn't know if there was something in the file's structure/format 
that could point to where the new data is (I'm not at all fmailliar with 
the internal structures of the mdb file format - I've never even looked
at it).


Thanks,

Kyle

-- 

------------------------------------------------------------------------------
Wisdom and Compassion are inseparable.
        -- Christmas Humphreys
mo...@vo...                            http://www.voicenet.com/~mortis
------------------------------------------------------------------------------

Re: [mdb-dev] mdb-sql: Readline Completion Support

[Kyle R. B. <mo...@vo...>]

> Since I am basically just a lurker on this list, feel free to ignore
> these comments:
> 
> 1.)  It's generally easier to review patches if each patch does one
> thing.  i.e. you should keep your case insensitive SQL patch separate
> from your completion patch and attach both to your message if necessary.

That's good advice, thanks.  I had done several things in my local working 
copy of the software and didn't pay enough attention when I created the 
patch.  If the project wants the readline completion code, I can re-submit 
a patch based solely on that feature.

> 2.)  Gratuitous whitespace changes get in the way of what your patch is
> doing.  The reviewer has to waste time looking through the whitespace
> changes to see if you made any other changes in that section besides
> just the whitespace changes.

Another good point.  I had inadvertantly modified some lines while trying
to learn the code.  As you have pointed out, they shouldn't be included in
patches.  If either of these features are desired by the developers for
inclusion I can break them into their own patches.


Thank you for the advice.

Kyle R. Burton


-- 

------------------------------------------------------------------------------
Wisdom and Compassion are inseparable.
        -- Christmas Humphreys
mo...@vo...                            http://www.voicenet.com/~mortis
------------------------------------------------------------------------------

Re: [mdb-dev] mdb-sql: Readline Completion Support

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

Hi

Since I am basically just a lurker on this list, feel free to ignore
these comments:

1.)  It's generally easier to review patches if each patch does one
thing.  i.e. you should keep your case insensitive SQL patch separate
from your completion patch and attach both to your message if necessary.

2.)  Gratuitous whitespace changes get in the way of what your patch is
doing.  The reviewer has to waste time looking through the whitespace
changes to see if you made any other changes in that section besides
just the whitespace changes.

[snip]
>  int yywrap()
>  {
> -	return 1;
> +  return 1;

e.g. here.  There's no functional change.  This is just noise.

>  void yyerror(char *s)
>  {
> -	fprintf(stderr,"Error at Line : %s near %s\n", s, yytext);
> +  fprintf(stderr,"Error at Line : %s near %s\n", s, yytext);

And here too.

>  #if 0
>  int main(int argc, char **argv)
>  {
>  int i;
>  
> -	g_sql = mdb_sql_init();
> -	yyin = stdin;
> -	if (yyparse()) {
> -		fprintf(stderr, "Couldn't parse SQL\n");
> -		exit(1);
> -	}
> -	mdb_sql_dump(g_sql);
> -	mdb_sql_exit(g_sql);	
> +  g_sql = mdb_sql_init();
> +  yyin = stdin;
> +  if (yyparse()) {
> +    fprintf(stderr, "Couldn't parse SQL\n");
> +    exit(1);
> +  }
> +  mdb_sql_dump(g_sql);
> +  mdb_sql_exit(g_sql);  
[snip]

And the same here.

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

[mdb-dev] mdb-sql: Readline Completion Support

[Kyle R. B. <mo...@vo...>]

I've been using mdb-sql and since you've already got basic readline
support, I went and added in completion support to the shell.

I looked at what mdb-tables was doing to list the tables in the database
catalog and implemented similar functionality so table names are
included in the completion list.

The way the completion is implemented, it will only return candidates if
you've typed at least the first letter (or more) of one of the words.  If
the sql parsing strategy were changed so that partial parses could be 
recognized, then we could start looking at state-based completion - 
the idea being if you type: 'select ' and then hit tab, only table
names should be considered (and at that point a double tab could
just return the list of all of the tables).

A patch should be attached.


Best regards,
Kyle



-- 

------------------------------------------------------------------------------
Wisdom and Compassion are inseparable.
        -- Christmas Humphreys
mo...@vo...                            http://www.voicenet.com/~mortis
------------------------------------------------------------------------------

Re: [mdb-dev] MDB-Tools and Perl

[Kyle R. B. <mo...@vo...>]

> I am curious as to the ways in which one can interact with mdb-tools from 
> within a perl script?  I am not a strong programmer.  I can use the system 
> command from perl to start the command line utilities but can not pass it the 
> required information.  Does anyone have much experience of working with both 
> MDB tools and perl?

We have used MDB tools from Perl to list the tables in an MDB (using 
mdb-tables), and get all the records from a table (using mdb-export).

We either used backticks or open to read from those commands.  A direct call
to the C functions (libmdb) would probably be a better long teram solution
(DBD::mdbtools would be even better).

Pseudo code for we're using looks like:

# returns an array of table names
sub list_tables
{
    my($fileName) = @_;
    my $cmd = "mdb-tables $fileName";
    my $output = `$cmd`;
    if( 0 != ($? >> 8) ) {
        die "Error obtaining tables list [$cmd]: $output : \$!=>$! : \$?=>$?";
    }
    my @lines = split(/[\s\r\n]+/,$output);
    return @lines;
}

# returns an array of arrayrefs (array of records)
sub get_records
{
    my($fileName,$tableName) = @_;
    my $cmd = "mdb-export -d'\t' -Q $fileName '$tableName' |;
    my $fh;
    unless( open( $fh, $cmd ) ) {
        die "Error opening mdb read handle: $! : cmd: '$cmd'";
    }
    my @lines = <$fh>;
    close $fh;
    my @records;
    foreach my $line ( @lines ) {
        my @fields = split('\t',$line);
        $fields[-1] =~ s/[\r\n]+//;
        push @records, \@fields;
    }
    return @records;
}



-- 

------------------------------------------------------------------------------
Wisdom and Compassion are inseparable.
        -- Christmas Humphreys
mo...@vo...                            http://www.voicenet.com/~mortis
------------------------------------------------------------------------------

[mdb-dev] MDB-Tools and Perl

[RI D. <s02...@sm...>]

Hi,

I am curious as to the ways in which one can interact with mdb-tools from 
within a perl script?  I am not a strong programmer.  I can use the system 
command from perl to start the command line utilities but can not pass it the 
required information.  Does anyone have much experience of working with both 
MDB tools and perl?

Kind Regards,

Rob

Re: [mdb-dev] java and mdbtools: is it possible?

[mayur k <ma...@pr...>]

Hi , 
I have done some of the mdb hacking and have written the
code in java.The documentation was helpful for the same.
So my code is same what mdb-tools is in C.
But the java code is nowhere near what is possible in C.

Bye Mayur.
-----------------------------------------------------
Date: Fri, 1 Aug 2003 09:59:57 +0200
From: Michael Wood <mw...@it...>

To: Gerson Souza <d34...@ya...>

Cc: mdb...@li...

Subject: Re: [mdb-dev] java and mdbtools: is it possible?

On Thu, Jul 31, 2003 at 09:48:07AM -0300, Gerson Souza wrote:
> Hi all!
> 
>    I'm the guy that post an email about this subjects
> "java and mdbtools: is it possible?".
>    How did nobody reply me, I'm wondering whether I
> post in wrong list, because this is just for
> development issues. If I'm correct, could you indicate
> in which mailing list/forum/newsgroup I should post
> that email?
> 
>    Thanks a lot! I look forward to hearing from you.
[snip]

Hi

This is a very low traffic list.  It is probably the right list to
post
your question, but it's possible that nobody on this list knows the
answer.

You might have more luck if you use mdb-export or something on the
files
and import them into PostgreSQL/MySQL or something else and then use
that from Java.

-- 
__________________________________________________________
Sign-up for your own FREE Personalized E-mail at Mail.com
http://www.mail.com/?sr=signup

CareerBuilder.com has over 400,000 jobs. Be smarter about your job search
http://corp.mail.com/careers

Re: [mdb-dev] java and mdbtools: is it possible?

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

On Thu, Jul 31, 2003 at 09:48:07AM -0300, Gerson Souza wrote:
> Hi all!
> 
>    I'm the guy that post an email about this subjects
> "java and mdbtools: is it possible?".
>    How did nobody reply me, I'm wondering whether I
> post in wrong list, because this is just for
> development issues. If I'm correct, could you indicate
> in which mailing list/forum/newsgroup I should post
> that email?
> 
>    Thanks a lot! I look forward to hearing from you.
[snip]

Hi

This is a very low traffic list.  It is probably the right list to post
your question, but it's possible that nobody on this list knows the
answer.

You might have more luck if you use mdb-export or something on the files
and import them into PostgreSQL/MySQL or something else and then use
that from Java.

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

[mdb-dev] mdb-sql and underscores in table/column names

[Kyle R. B. <mo...@vo...>]

Hello.

We just downloaded and started testing mdbtools - it looks like you've done
alot of work on it since we last looked at it.  The ability to read data
from tables in MDB files is wonderful.  Thank you.

When working with the mdb-sql tool, I ran into the already known underscore
issue with table and column names.  I looked at the code and found where
the issue was and fixed it.  I've attached a patch for src/sql/lexer.l that
adds underscore support to both NAME and IDENT.  It also has a kind of hack
that allows for case insensitive support for the keywords.


Has anyone started on a Perl DBI driver with libmdb as the basis?

Thanks again,
Kyle R. Burton


-- 

------------------------------------------------------------------------------
Wisdom and Compassion are inseparable.
        -- Christmas Humphreys
mo...@vo...                            http://www.voicenet.com/~mortis
------------------------------------------------------------------------------

Re: [mdb-dev] java and mdbtools: is it possible?

[<d34...@ya...>]

Hi all!

   I'm the guy that post an email about this subjects
"java and mdbtools: is it possible?".
   How did nobody reply me, I'm wondering whether I
post in wrong list, because this is just for
development issues. If I'm correct, could you indicate
in which mailing list/forum/newsgroup I should post
that email?

   Thanks a lot! I look forward to hearing from you.

P.S.: Again... sorry about grammar/spell errors.

 --- Gerson Souza <d34...@ya...>
escreveu: > Hi all!
> 
> I have the following problem: a web application in a
> Java / Tomcat / Linux environment. This application
> is
> feed by .mdb files, weekly.
> 
> After searching (a lot) on web how I could read
> these
> files, I found your project. Howerver, I'm having
> several doubts in using its odbc features.
> 
> First I install unixodbc and configure it like this:
> 
> ODBC.INI: 
> ... 
> [MyDB] 
> Description = MyDB 
> Driver = MDBToolsODBC 
> Database = /home/gsouza/MyDB.mdb 
> Servername = localhost 
> UserName = 
> Password = 
> Port = 5432 
> 
> ODBCINST.INI: 
> 
> [MDBToolsODBC] 
> Description = MDB Tools ODBC drivers 
> Driver = /usr/local/lib/libmdbodbc.so.0 
> Setup = 
> FileUsage = 1 
> CPTimeout = 
> CPReuse = 
>  
> Then, i installed rpms of mdbtools.
> 
> After that, I did some test using mdb-* utils and It
> worked ok.
> 
> Finally, I begun my first java test, using jdbcOdbc
> bridge, to access the .mdb: 
> 
> import java.sql.*;
> class TestDB
> {
>   public static void main (String args[])
>   {
>     String url = "jdbc:odbc:MyDB";
>     try
>     {
>       Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
>       Connection conn = DriverManager.getConnection
> (url, "", "");
>       .........
> 
> 
> It compiles without problems, but at runtime it
> throws
> a NullPointerException on
> DriverManager.getConnection
> method.
> 
> So I tried the dns-less way, like:
> 
> String url = "DRIVER={MDB Tools ODBC drivers};
> DBQ=/home/gsouza/MyDB.mdb" 
> 
> String url = "DRIVER={MDBToolsODBC};
> DBQ=/home/gsouza/MyDB.mdb"
> 
> String url =
> "DRIVER={/usr/local/lib/libmdbodbc.so.0};
> DBQ=/home/gsouza/MyDB.mdb"
> 
>    
> Nevertheless, none worked.
> Thus, if anyone that have been successful in java +
> mdbtools figure out what I'm doing wrong I'd
> appreciate.
> 
> Thank you.
> 
> P.S.: I'm sorry cause of grammar errors. I'm not an
> english native speaker.
> 
> 
> 
> 
> 
> 
> 
>
_______________________________________________________________________
> Conheça o novo Cadê? - Mais rápido, mais fácil e
> mais preciso.
> Toda a web, 42 milhões de páginas brasileiras e nova
> busca por imagens!
> http://www.cade.com.br
> 
> 
>
-------------------------------------------------------
> This SF.Net email sponsored by: Free pre-built
> ASP.NET sites including
> Data Reports, E-commerce, Portals, and Forums are
> available now.
> Download today and enter to win an XBOX or Visual
> Studio .NET.
>
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
> _______________________________________________
> mdbtools-dev mailing list
> mdb...@li...
>
https://lists.sourceforge.net/lists/listinfo/mdbtools-dev 

_______________________________________________________________________
Conheça o novo Cadê? - Mais rápido, mais fácil e mais preciso.
Toda a web, 42 milhões de páginas brasileiras e nova busca por imagens!
http://www.cade.com.br

[mdb-dev] Use of "LIKE"

[Nicola Q. <ni...@qu...>]

Hi,
Someone is successful to use "LIKE" with driver the ODBC ?

It seems that not functions.

I have tried version mdbtools-0.5rc2.

Tanks.
Nicola.

-- 
Quargentan S.p.A.
Nicola Quargentan

Re: [mdb-dev] Seg fault and CVS problems

[David M. <mdb...@dm...>]

> David, I'm confused as to what's happening. I got this note from you
> today, through the mdbtools-dev list. However, it didn't have an
> attachment. I received a previous note from you on the 21st, with a
> slightly different body text and with a patch called
> 'mdbtools-combined.patch.'
> 
> Using the patch from the 21st, I began from the beginning, with untarring, etc., and still had some problems. I've enclosed the whole, long output of what I did, in the hope of furthering development on mdb-tools. The output was:
> kevinz@www:~$ tar -zxvf mdbtools-0.5rc2.tar.gz 

[ cut ]

> kevinz@www:~/mdbtools-0.5rc2$ make
> Making all in src
> make[1]: Entering directory `/home/kevinz/mdbtools-0.5rc2/src'
> Making all in libmdb
> make[2]: Entering directory `/home/kevinz/mdbtools-0.5rc2/src/libmdb'
> cd ../.. && \
>   automake-1.6 --gnu  src/libmdb/Makefile
> /bin/sh: automake-1.6: command not found
> make[2]: *** [Makefile.in] Error 127
> make[2]: Leaving directory `/home/kevinz/mdbtools-0.5rc2/src/libmdb'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/home/kevinz/mdbtools-0.5rc2/src'
> make: *** [all-recursive] Error 1
> kevinz@www:~/mdbtools-0.5rc2$ 
> 

Oh.  Interesting.  I don't know a whole lot about automake and autoconf, 
but it seems as though I've excluded part of the diff to the (generated) 
file Makefile.in.

I suggest completely removing the old directory and starting again, this 
time using the newer version of the combined patch that I have attached to 
this email.  This patch includes the diff to the Makefile.in which was 
missing from the prior patch.

It *seems* to work for me (but I have always had the automake installed 
:-)

Give it a try, and again, let me know either way if it works.
David

-- 
/==============================\
| David Mansfield              |
| mdb...@db...       |
\==============================/

Re: [mdb-dev] Seg fault and CVS problems

[KEVIN Z. <KZE...@jh...>]

David, I'm confused as to what's happening. I got this note from you =
today, through the mdbtools-dev list. However, it didn't have an attachment=
. I received a previous note from you on the 21st, with a slightly =
different body text and with a patch called 'mdbtools-combined.patch.'

Using the patch from the 21st, I began from the beginning, with untarring, =
etc., and still had some problems. I've enclosed the whole, long output of =
what I did, in the hope of furthering development on mdb-tools. The output =
was:
kevinz@www:~$ tar -zxvf mdbtools-0.5rc2.tar.gz=20
mdbtools-0.5rc2/
mdbtools-0.5rc2/README
mdbtools-0.5rc2/AUTHORS
mdbtools-0.5rc2/COPYING
mdbtools-0.5rc2/COPYING.LIB
mdbtools-0.5rc2/ChangeLog
mdbtools-0.5rc2/INSTALL
mdbtools-0.5rc2/Makefile.am
mdbtools-0.5rc2/Makefile.in
mdbtools-0.5rc2/NEWS
mdbtools-0.5rc2/TODO
mdbtools-0.5rc2/acinclude.m4
mdbtools-0.5rc2/aclocal.m4
mdbtools-0.5rc2/config.guess
mdbtools-0.5rc2/config.sub
mdbtools-0.5rc2/configure
mdbtools-0.5rc2/configure.in
mdbtools-0.5rc2/depcomp
mdbtools-0.5rc2/install-sh
mdbtools-0.5rc2/ltmain.sh
mdbtools-0.5rc2/mdbtools.spec.in
mdbtools-0.5rc2/missing
mdbtools-0.5rc2/mkinstalldirs
mdbtools-0.5rc2/HACKING
mdbtools-0.5rc2/src/
mdbtools-0.5rc2/src/Makefile.am
mdbtools-0.5rc2/src/Makefile.in
mdbtools-0.5rc2/src/libmdb/
mdbtools-0.5rc2/src/libmdb/Makefile.am
mdbtools-0.5rc2/src/libmdb/Makefile.in
mdbtools-0.5rc2/src/libmdb/catalog.c
mdbtools-0.5rc2/src/libmdb/mem.c
mdbtools-0.5rc2/src/libmdb/file.c
mdbtools-0.5rc2/src/libmdb/kkd.c
mdbtools-0.5rc2/src/libmdb/table.c
mdbtools-0.5rc2/src/libmdb/data.c
mdbtools-0.5rc2/src/libmdb/dump.c
mdbtools-0.5rc2/src/libmdb/backend.c
mdbtools-0.5rc2/src/libmdb/money.c
mdbtools-0.5rc2/src/libmdb/sargs.c
mdbtools-0.5rc2/src/libmdb/index.c
mdbtools-0.5rc2/src/libmdb/like.c
mdbtools-0.5rc2/src/libmdb/write.c
mdbtools-0.5rc2/src/libmdb/stats.c
mdbtools-0.5rc2/src/extras/
mdbtools-0.5rc2/src/extras/Makefile.am
mdbtools-0.5rc2/src/extras/Makefile.in
mdbtools-0.5rc2/src/extras/mdb-dump.c
mdbtools-0.5rc2/src/extras/mdbsupport.c
mdbtools-0.5rc2/src/sql/
mdbtools-0.5rc2/src/sql/Makefile.am
mdbtools-0.5rc2/src/sql/Makefile.in
mdbtools-0.5rc2/src/sql/mdbsql.c
mdbtools-0.5rc2/src/sql/parser.y
mdbtools-0.5rc2/src/sql/lexer.l
mdbtools-0.5rc2/src/odbc/
mdbtools-0.5rc2/src/odbc/connectparams.h
mdbtools-0.5rc2/src/odbc/Makefile.am
mdbtools-0.5rc2/src/odbc/Makefile.in
mdbtools-0.5rc2/src/odbc/odbc.c
mdbtools-0.5rc2/src/odbc/connectparams.c
mdbtools-0.5rc2/src/odbc/unittest.c
mdbtools-0.5rc2/src/gmdb2/
mdbtools-0.5rc2/src/gmdb2/gmdb.h
mdbtools-0.5rc2/src/gmdb2/Makefile.am
mdbtools-0.5rc2/src/gmdb2/Makefile.in
mdbtools-0.5rc2/src/gmdb2/main2.c
mdbtools-0.5rc2/src/gmdb2/file.c
mdbtools-0.5rc2/src/gmdb2/util.c
mdbtools-0.5rc2/src/gmdb2/table.c
mdbtools-0.5rc2/src/gmdb2/query.c
mdbtools-0.5rc2/src/gmdb2/module.c
mdbtools-0.5rc2/src/gmdb2/macro.c
mdbtools-0.5rc2/src/gmdb2/report.c
mdbtools-0.5rc2/src/gmdb2/form.c
mdbtools-0.5rc2/src/gmdb2/info.c
mdbtools-0.5rc2/src/gmdb2/table_def.c
mdbtools-0.5rc2/src/gmdb2/table_data.c
mdbtools-0.5rc2/src/gmdb2/table_export.c
mdbtools-0.5rc2/src/gmdb2/debug.c
mdbtools-0.5rc2/src/gmdb2/sql.c
mdbtools-0.5rc2/src/gmdb2/schema.c
mdbtools-0.5rc2/src/gmdb2/prefs.c
mdbtools-0.5rc2/src/gmdb2/help/
mdbtools-0.5rc2/src/gmdb2/help/Makefile.am
mdbtools-0.5rc2/src/gmdb2/help/Makefile.in
mdbtools-0.5rc2/src/gmdb2/help/C/
mdbtools-0.5rc2/src/gmdb2/help/C/figures/
mdbtools-0.5rc2/src/gmdb2/help/C/figures/gmdb2_window.png
mdbtools-0.5rc2/src/gmdb2/help/C/Makefile.am
mdbtools-0.5rc2/src/gmdb2/help/C/Makefile.in
mdbtools-0.5rc2/src/gmdb2/help/C/xmldocs.make
mdbtools-0.5rc2/src/gmdb2/help/C/legal.xml
mdbtools-0.5rc2/src/gmdb2/help/C/gmdb.xml
mdbtools-0.5rc2/src/gmdb2/help/C/gmdb-C.omf
mdbtools-0.5rc2/src/gmdb2/gladefiles/
mdbtools-0.5rc2/src/gmdb2/gladefiles/Makefile.am
mdbtools-0.5rc2/src/gmdb2/gladefiles/Makefile.in
mdbtools-0.5rc2/src/gmdb2/gladefiles/gmdb.glade
mdbtools-0.5rc2/src/gmdb2/gladefiles/gmdb-sql.glade
mdbtools-0.5rc2/src/gmdb2/gladefiles/gmdb-sql-file.glade
mdbtools-0.5rc2/src/gmdb2/gladefiles/gmdb-debug.glade
mdbtools-0.5rc2/src/gmdb2/gladefiles/gmdb-export.glade
mdbtools-0.5rc2/src/gmdb2/gladefiles/gmdb-schema.glade
mdbtools-0.5rc2/src/gmdb2/gladefiles/gmdb-prefs.glade
mdbtools-0.5rc2/src/gmdb2/gladefiles/gmdb-props.glade
mdbtools-0.5rc2/src/gmdb2/pixmaps/
mdbtools-0.5rc2/src/gmdb2/pixmaps/Makefile.am
mdbtools-0.5rc2/src/gmdb2/pixmaps/Makefile.in
mdbtools-0.5rc2/src/gmdb2/pixmaps/pk.xpm
mdbtools-0.5rc2/src/gmdb2/pixmaps/logo.xpm
mdbtools-0.5rc2/src/gmdb2/pixmaps/debug.xpm
mdbtools-0.5rc2/src/gmdb2/pixmaps/table.xpm
mdbtools-0.5rc2/src/gmdb2/pixmaps/query.xpm
mdbtools-0.5rc2/src/gmdb2/pixmaps/forms.xpm
mdbtools-0.5rc2/src/gmdb2/pixmaps/reports.xpm
mdbtools-0.5rc2/src/gmdb2/pixmaps/macros.xpm
mdbtools-0.5rc2/src/gmdb2/pixmaps/code.xpm
mdbtools-0.5rc2/src/gmdb2/pixmaps/table_big.xpm
mdbtools-0.5rc2/src/gmdb2/pixmaps/query_big.xpm
mdbtools-0.5rc2/src/gmdb2/pixmaps/form_big.xpm
mdbtools-0.5rc2/src/gmdb2/pixmaps/report_big.xpm
mdbtools-0.5rc2/src/gmdb2/pixmaps/macro_big.xpm
mdbtools-0.5rc2/src/gmdb2/pixmaps/module_big.xpm
mdbtools-0.5rc2/src/gmdb2/pixmaps/stock_export.png
mdbtools-0.5rc2/src/gmdb2/pixmaps/stock_export-16.png
mdbtools-0.5rc2/src/util/
mdbtools-0.5rc2/src/util/Makefile.am
mdbtools-0.5rc2/src/util/Makefile.in
mdbtools-0.5rc2/src/util/mdb-array.c
mdbtools-0.5rc2/src/util/mdb-export.c
mdbtools-0.5rc2/src/util/mdb-header.c
mdbtools-0.5rc2/src/util/mdb-parsecsv.c
mdbtools-0.5rc2/src/util/mdb-schema.c
mdbtools-0.5rc2/src/util/mdb-sql.c
mdbtools-0.5rc2/src/util/mdb-tables.c
mdbtools-0.5rc2/src/util/mdb-ver.c
mdbtools-0.5rc2/src/util/prcat.c
mdbtools-0.5rc2/src/util/prdata.c
mdbtools-0.5rc2/src/util/prdump.c
mdbtools-0.5rc2/src/util/prindex.c
mdbtools-0.5rc2/src/util/prkkd.c
mdbtools-0.5rc2/src/util/prole.c
mdbtools-0.5rc2/src/util/prtable.c
mdbtools-0.5rc2/src/util/updrow.c
mdbtools-0.5rc2/include/
mdbtools-0.5rc2/include/mdbtools.h
mdbtools-0.5rc2/include/mdbsql.h
mdbtools-0.5rc2/include/mdbodbc.h
mdbtools-0.5rc2/include/Makefile.am
mdbtools-0.5rc2/include/Makefile.in
mdbtools-0.5rc2/doc/
mdbtools-0.5rc2/doc/Makefile.am
mdbtools-0.5rc2/doc/Makefile.in
mdbtools-0.5rc2/doc/mdb-tables.txt
mdbtools-0.5rc2/doc/mdb-ver.txt
mdbtools-0.5rc2/doc/mdb-export.txt
mdbtools-0.5rc2/doc/mdb-schema.txt
mdbtools-0.5rc2/doc/mdb-sql.txt
mdbtools-0.5rc2/doc/faq.html
mdbtools-0.5rc2/doc/txt2man
kevinz@www:~$ cd mdbtools-0.5rc2
kevinz@www:~/mdbtools-0.5rc2$ ls -l # After ftping combined-patch from =
email.
total 988
-rw-r--r--    1 kevinz   wwwadmin      515 Oct 13  2000 AUTHORS
-rw-r--r--    1 kevinz   wwwadmin    17989 Feb 12  2000 COPYING
-rwxr-xr-x    1 kevinz   wwwadmin    25265 Feb 12  2000 COPYING.LIB
-rw-r--r--    1 kevinz   wwwadmin     1435 Apr  8  2002 ChangeLog
-rw-r--r--    1 kevinz   wwwadmin    29619 Jan 12  2003 HACKING
-rw-r--r--    1 kevinz   wwwadmin     3148 Dec 27  2002 INSTALL
-rw-r--r--    1 kevinz   wwwadmin       69 Jan 12  2003 Makefile.am
-rw-r--r--    1 kevinz   wwwadmin    13627 Jan 15  2003 Makefile.in
-rw-r--r--    1 kevinz   wwwadmin      209 Apr 11  2001 NEWS
-rw-r--r--    1 kevinz   wwwadmin     1450 Apr 14  2002 README
-rw-r--r--    1 kevinz   wwwadmin     1278 Jan  5  2003 TODO
-rw-r--r--    1 kevinz   wwwadmin   117758 Dec 27  2002 acinclude.m4
-rw-r--r--    1 kevinz   wwwadmin   155048 Jan 15  2003 aclocal.m4
-rwxr-xr-x    1 kevinz   wwwadmin    38504 Jan 15  2003 config.guess
-rwxr-xr-x    1 kevinz   wwwadmin    28224 Jan 15  2003 config.sub
-rwxr-xr-x    1 kevinz   wwwadmin   306080 Jan 15  2003 configure
-rw-r--r--    1 kevinz   wwwadmin     3045 Jan 15  2003 configure.in
-rwxr-xr-x    1 kevinz   wwwadmin    12123 Jul 29  2002 depcomp
drwxr-xr-x    2 kevinz   wwwadmin     4096 Jan 15  2003 doc
drwxr-xr-x    2 kevinz   wwwadmin     4096 Jan 15  2003 include
-rwxr-xr-x    1 kevinz   wwwadmin     5598 Apr 15  2001 install-sh
-rw-r--r--    1 kevinz   wwwadmin   141392 Jan 15  2003 ltmain.sh
-rw-r--r--    1 kevinz   wwwadmin    20207 Jul 28 10:57 mdbtools-combined.p=
atch
-rw-r--r--    1 kevinz   wwwadmin     2827 Jan 15  2003 mdbtools.spec.in
-rwxr-xr-x    1 kevinz   wwwadmin     6283 Apr 15  2001 missing
-rwxr-xr-x    1 kevinz   wwwadmin      724 Apr 15  2001 mkinstalldirs
drwxr-xr-x    8 kevinz   wwwadmin     4096 Jan 15  2003 src
kevinz@www:~/mdbtools-0.5rc2$ patch -p1 <mdbtools-combined.patch=20
patching file include/mdbtools.h
patching file src/libmdb/backend.c
patching file src/libmdb/data.c
patching file src/libmdb/file.c
patching file src/libmdb/Makefile.am
patching file src/libmdb/mem.c
patching file src/libmdb/table.c
patching file src/util/mdb-export.c
patching file src/util/mdb-schema.c
kevinz@www:~/mdbtools-0.5rc2$ ./configure --enable-sql --with-unixodbc=3D/u=
sr/local
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
/home/kevinz/mdbtools-0.5rc2/missing: Unknown `--run' option
Try `/home/kevinz/mdbtools-0.5rc2/missing --help' for more information
configure: WARNING: `missing' script is too old or missing
checking for gawk... gawk
checking whether make sets ${MAKE}... yes
checking for gcc... gcc
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...=20
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for style of include used by make... GNU
checking dependency style of gcc... gcc
checking whether make sets ${MAKE}... (cached) yes
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for ld used by GCC... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for /usr/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognise dependant libraries... pass_all
checking command to parse /usr/bin/nm -B output... ok
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for ranlib... ranlib
checking for strip... strip
checking for objdir... .libs
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.lo... yes
checking if gcc supports -fno-rtti -fno-exceptions... yes
checking whether the linker (/usr/bin/ld) supports shared libraries... yes
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking whether -lc should be explicitly linked in... no
creating libtool
checking for flex... flex
checking for yywrap in -lfl... yes
checking lex output file root... lex.yy
checking whether yytext is a pointer... yes
checking for bison... bison -y
checking for ANSI C header files... (cached) yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking limits.h usability... yes
checking limits.h presence... yes
checking for limits.h... yes
checking for unistd.h... (cached) yes
checking wordexp.h usability... yes
checking wordexp.h presence... yes
checking for wordexp.h... yes
checking for gcc option to accept ANSI C... none needed
checking for an ANSI C-conforming const... yes
checking for size_t... yes
checking whether byte ordering is bigendian... no
checking Are we using flex ... yes=20
checking for pkg-config... /usr/bin/pkg-config
checking for GLIB - version >=3D 2.0.0... yes (version 2.0.1)
checking for libglade-2.0 libgnomeui-2.0... Package libgnomeui-2.0 was not =
found in the pkg-config search path.
Perhaps you should add the directory containing `libgnomeui-2.0.pc'
to the PKG_CONFIG_PATH environment variable
No package 'libgnomeui-2.0' found
checking for initscr in -lncurses... no
checking for add_history in -lreadline... no
configure: creating ./config.status
config.status: creating src/Makefile
config.status: creating src/util/Makefile
config.status: creating src/extras/Makefile
config.status: creating Makefile
config.status: creating include/Makefile
config.status: creating src/Makefile
config.status: creating src/libmdb/Makefile
config.status: creating include/Makefile
config.status: creating src/sql/Makefile
config.status: creating src/odbc/Makefile
config.status: creating doc/Makefile
config.status: creating src/gmdb2/Makefile
config.status: creating src/gmdb2/gladefiles/Makefile
config.status: creating src/gmdb2/pixmaps/Makefile
config.status: creating src/gmdb2/help/Makefile
config.status: creating src/gmdb2/help/C/Makefile
config.status: creating mdbtools.spec
config.status: executing depfiles commands
kevinz@www:~/mdbtools-0.5rc2$ make
Making all in src
make[1]: Entering directory `/home/kevinz/mdbtools-0.5rc2/src'
Making all in libmdb
make[2]: Entering directory `/home/kevinz/mdbtools-0.5rc2/src/libmdb'
cd ../.. && \
  automake-1.6 --gnu  src/libmdb/Makefile
/bin/sh: automake-1.6: command not found
make[2]: *** [Makefile.in] Error 127
make[2]: Leaving directory `/home/kevinz/mdbtools-0.5rc2/src/libmdb'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/kevinz/mdbtools-0.5rc2/src'
make: *** [all-recursive] Error 1
kevinz@www:~/mdbtools-0.5rc2$=20

Thank you for your contined help on this project.

-Kevin Zembower

-----
E. Kevin Zembower
Unix Administrator
Johns Hopkins University/Center for Communications Programs
111 Market Place, Suite 310
Baltimore, MD  21202
410-659-6139

>>> David Mansfield <mdb...@dm...> 07/28/03 09:55AM >>>


Kevin,

Try re-building the programs after applying the attached patch.  It =
fixes=20
a handful of known segfault causing bugs.  I can't guarantee it'll work=20
for you but...

Untar the source as before, then from inside the source directory:

patch -p1 < mdbtools-combined.patch

Then configure, build and install as usual.

Let me know if this does/doesn't work for you.=20

Thanks,
David

--=20
/=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D\
| David Mansfield              |
| mdb...@db...       |
\=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D/

[mdb-dev] what is wrong here? dsn not found?

[Luis M. C. M. <lu...@b2...>]

Why is the reason of this error:

# php cargaODBC.php
Content-type: text/html

<HTML><BODY>Couldn't find DSN /root/.odbc.ini in Microsoft Access
LookupDSN: LoadDSN returned FALSE[unixODBC]Could not find DSN in=20
odbc.ini[root@www1 html]#

We don't have this problem from apache web server.
Can aynone explain us the reasons or the solution?


Luis Miguel Cruz Miranda.               |       B2B INTEGRAL, S.A.
CCNA - Systems Administrator            |       Pol. Ind. de Asipo
                                         |       C/A - Parcela 86-C
Tel: +34 902 506 605                    |       33.428 - CAYES - LLANERA
Fax:+34 985 980 794                     |       ASTURIAS (ESPA=D1A/SPAIN)

AVISO SOBRE CONFIDENCIALIDAD: Este mensaje y en su caso, sus anexos, se
dirige exclusivamente a su destinatario, por poder contener informaci=F3n
confidencial sometida a secreto profesional o cuya divulgaci=F3n est=E9
prohibida en virtud de la legislaci=F3n vigente, se informa a qui=E9n lo
recibiera sin ser el destinatario o persona autorizada por =E9ste, que la
informaci=F3n contenida en el mismo es reservada y su utilizaci=F3n o
divulgaci=F3n con cualquier fin est=E1 prohibida. Si ha recibido este
documento por error, le rogamos que nos lo comunique a la mayor brevedad
posible y proceda a su destrucci=F3n. =20

Re: [mdb-dev] Seg fault and CVS problems

[David M. <mdb...@dm...>]

> Then, I got the 0.5rc2 tarball and did the dance: tar zxvf mdbtools-0.5rc2.tar.gz; cd mdbtools-0.5rc2/; ./configure --enable-sql; make; su -; make install. All seemed to go well, except for some complaints about missing libglade and libgnomeui, which didn't stop the build. mdbtools seems to be working, except for a Segmentation fault when the '-H' (omit the header row) is used:
> kevinz@www:~/budgetdb$ mdb-export budgettables.mdb BCODE | head -3   
> BUDGETNUMB,BUDGETDESC,THRU_DATE,FROM_DATE,ACTIVE_INA,AT_T_CODE,AWARD_NUMB,ON_OFF_CAM,OLD_BUDGET,BREGION,FUNDING,FINANALYST,PROGOFFICE,DATERECORD,DATELASTMO,TIMELASTM9,LASTMODIFI,TIMERECTM9,CREATEDBYO,MASTERACCO,TYPEFUNDIN,COUNTRY,OLDAUTHCODE,FUND,AREAORG,NOTES,TEAM
> 8050104.000000,"Popdynamics GF","","","I",,2,"On Campus","","Admin","CCP","vsmith","","08/23/96 00:00:00","06/12/97 00:00:00","07443677","CGK","13494660","DTN",8850105.000000,"","Nepal",,690,,"",
> 9800131.000000,"General Funds '04","06/30/04 00:00:00","07/01/00 00:00:00","A",2398613.000000,,"On Campus","H-32-0005","Admin","CCP","vsmith","SHD","","11/29/00 00:00:00","13541336","CGK","","",9800131.000000,"Discretionary","Non-Country",9416,0,,"Requires prior approval by Susan",
> kevinz@www:~/budgetdb$ mdb-export -H budgettables.mdb BCODE
> Segmentation fault
> kevinz@www:~/budgetdb$ 
> 

Kevin,

Try re-building the programs after applying the attached patch.  It fixes 
a handful of known segfault causing bugs.  I can't guarantee it'll work 
for you but...

Untar the source as before, then from inside the source directory:

patch -p1 < mdbtools-combined.patch

Then configure, build and install as usual.

Let me know if this does/doesn't work for you. 

Thanks,
David

-- 
/==============================\
| David Mansfield              |
| mdb...@db...       |
\==============================/

[mdb-dev] java and mdbtools: is it possible?

[<d34...@ya...>]

Hi all!

I have the following problem: a web application in a
Java / Tomcat / Linux environment. This application is
feed by .mdb files, weekly.

After searching (a lot) on web how I could read these
files, I found your project. Howerver, I'm having
several doubts in using its odbc features.

First I install unixodbc and configure it like this:

ODBC.INI: 
... 
[MyDB] 
Description = MyDB 
Driver = MDBToolsODBC 
Database = /home/gsouza/MyDB.mdb 
Servername = localhost 
UserName = 
Password = 
Port = 5432 

ODBCINST.INI: 

[MDBToolsODBC] 
Description = MDB Tools ODBC drivers 
Driver = /usr/local/lib/libmdbodbc.so.0 
Setup = 
FileUsage = 1 
CPTimeout = 
CPReuse = 
 
Then, i installed rpms of mdbtools.

After that, I did some test using mdb-* utils and It
worked ok.

Finally, I begun my first java test, using jdbcOdbc
bridge, to access the .mdb: 

import java.sql.*;
class TestDB
{
  public static void main (String args[])
  {
    String url = "jdbc:odbc:MyDB";
    try
    {
      Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
      Connection conn = DriverManager.getConnection
(url, "", "");
      .........


It compiles without problems, but at runtime it throws
a NullPointerException on DriverManager.getConnection
method.

So I tried the dns-less way, like:

String url = "DRIVER={MDB Tools ODBC drivers};
DBQ=/home/gsouza/MyDB.mdb" 

String url = "DRIVER={MDBToolsODBC};
DBQ=/home/gsouza/MyDB.mdb"

String url = "DRIVER={/usr/local/lib/libmdbodbc.so.0};
DBQ=/home/gsouza/MyDB.mdb"

   
Nevertheless, none worked.
Thus, if anyone that have been successful in java +
mdbtools figure out what I'm doing wrong I'd
appreciate.

Thank you.

P.S.: I'm sorry cause of grammar errors. I'm not an
english native speaker.







_______________________________________________________________________
Conheça o novo Cadê? - Mais rápido, mais fácil e mais preciso.
Toda a web, 42 milhões de páginas brasileiras e nova busca por imagens!
http://www.cade.com.br

[mdb-dev] problem reading datetime set to "Long Time" in access

[Nick B. <sp...@2t...>]

I am having a problem reading a datatime access field that is set to =22L=
ong
Time=22.  In access all you see is the time (no date), and mdbtools seems=
 to
be reading this in such a way that all entries are interpreted as a very
early date.

For example in access I have these entries:
12:50:01 PM
12:51:13 PM
12:51:14 PM
12:57:43 PM

the mdbtools output for the field is this:
12/13/01 20:45:52
12/13/01 20:45:52
12/13/01 20:45:52
12/13/01 20:45:52

Another datetime field in the database set to =22short date=22 reads corr=
ectly
and doesn't seem to have any problems at all.

I am using the odbc driver, but I have tried the mdb-export utilit with
the same results.

I am using version 0.5rc2.  I have tried pulling down the latest cvs but =
I
cannot get it to compile.

Any ideas?  If anyone would like a look, I would be happy to send the
database.  It is about 130k zipped.