mdbtools-dev

Re: [mdb-dev] Truncated Memo fields - 255 characters

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

--- Brian McMillan <bm...@cq...> wrote:
> I've trawled the archives and from that have given up trying to use php
> and UnixODBC in conjunction with mdbtools due to the segfault issues
> that are mentioned by various correspondents.

Actually, I forgot to mail the list that I made some changes last week
which should have (mostly) corrected this issue.

  -- Jeff Smith


	
		
__________________________________ 
Do you Yahoo!? 
Yahoo! Mail - You care about security. So do we. 
http://promotions.yahoo.com/new_mail

[mdb-dev] Truncated Memo fields - 255 characters

[Brian M. <bm...@cq...>]

I've trawled the archives and from that have given up trying to use php
and UnixODBC in conjunction with mdbtools due to the segfault issues
that are mentioned by various correspondents.

I'm now using mdb-export and can drop a table into text format which I
can then parse apart from my memo fields which all get truncated. I
can't believe I'm the only person to be suffering this, but there are
only vague references to the problem. 

Am I missing something obvious, or do I have to get into the source
code?

Apart from that mdbtools is an ideal utility, well done!

many thanks in advance,

Brian.

[mdb-dev] mdbtools-java: truncated strings

[puma <pum...@we...>]

Hey Calvin, here's another one finding your java port very usefull.

So big thanks to you for making this one possible!


I got a little problem and hope you will be able to help.
I use mdbtools to query a mediamonkey (www.mediamonkey.com) database.
Everything worked fine till I upgraded to their new version. From then
on, some of the entries queried from "text fields" where truncated
at varying points.

Then I found out that they changed the field size of the textfields from
254 chars to 255. Resetting the field size to 254 chars by hand in access
solved the problem with the truncated strings queried from those textfields.

Is there anything I can do to read the new database version without
having to manually change the length in access?

Sorry if this is an obvious issue, I'm very new to programming and
databases.

Thanks in advance for your time
Achim



PS: I'm sorry, I just realized I send this email some minutes ago from another
account, which is not subscribed to the list. So whoever gets bothered with that
other mail, please excuse and delete it.

[mdb-dev] mdbtools-java: truncated strings

[Achim K. <ach...@we...>]

Hey Calvin, here's another one finding your java port very usefull.

So big thanks to you for making this one possible!


I got a little problem and hope you will be able to help.
I use mdbtools to query a mediamonkey (www.mediamonkey.com) database.
Everything worked fine till I upgraded to their new version. From then
on, some of the entries queried from "text fields" where truncated
at varying points.

Then I found out that they changed the field size of the textfields from
254 chars to 255. Resetting the field size to 254 chars by hand in access
solved the problem with the truncated strings queried from those textfields.

Is there anything I can do to read the new database version without
having to manually change the length in access?

Sorry if this is an obvious issue, I'm very new to programming and
databases.

Thanks in advance for your time
Achim

[mdb-dev] Fixes to glade files

[Edward C. <ed...@ca...>]

This attachment contains fixes to let gmdb2 windows display toolbars
properly, and fixes the schema export window.

Re: [mdb-dev] Deleted columns in Jet3 database

[Edward C. <ed...@ca...>]

Thanks! I'll test it once you've made the change - do you want the
database?

Ed

On Fri, 2005-02-25 at 17:05 -0800, Jeff Smith wrote:
>Ed,
>
>I never made the change for Jet3, because I didn't have a test case.
>Actually, as I have it, three lines should change.  I will attempt to
>commit it tonight.
>
> -- Jeff Smith
>
>
>--- Edward Catmur <ed...@ca...> wrote:
>
>> I have a Jet3 database with a large number of deleted columns (34
>> deleted columns of 46 total). All the non-deleted columns are variable
>> width.
>> 
>> When mdbtools reads the rows, it appears to use the wrong column index -
>> the index of the column within the non-deleted columns, not the index
>> within all columns. As a result the column offset and width get set to 0
>> and the data is not read.
>> 
>> I'll attach the small patch I used; I can send the database in question
>> if you want but I don't want to post it to the list.
>> 
>> Thanks,
>> 
>> Ed
>
>
>	
>		
>__________________________________ 
>Do you Yahoo!? 
>Yahoo! Mail - You care about security. So do we. 
>http://promotions.yahoo.com/new_mail

Re: [mdb-dev] Deleted columns in Jet3 database

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

Ed,

I never made the change for Jet3, because I didn't have a test case.
Actually, as I have it, three lines should change.  I will attempt to
commit it tonight.

 -- Jeff Smith


--- Edward Catmur <ed...@ca...> wrote:

> I have a Jet3 database with a large number of deleted columns (34
> deleted columns of 46 total). All the non-deleted columns are variable
> width.
> 
> When mdbtools reads the rows, it appears to use the wrong column index -
> the index of the column within the non-deleted columns, not the index
> within all columns. As a result the column offset and width get set to 0
> and the data is not read.
> 
> I'll attach the small patch I used; I can send the database in question
> if you want but I don't want to post it to the list.
> 
> Thanks,
> 
> Ed


	
		
__________________________________ 
Do you Yahoo!? 
Yahoo! Mail - You care about security. So do we. 
http://promotions.yahoo.com/new_mail

[mdb-dev] Deleted columns in Jet3 database

[Edward C. <ed...@ca...>]

I have a Jet3 database with a large number of deleted columns (34
deleted columns of 46 total). All the non-deleted columns are variable
width.

When mdbtools reads the rows, it appears to use the wrong column index -
the index of the column within the non-deleted columns, not the index
within all columns. As a result the column offset and width get set to 0
and the data is not read.

I'll attach the small patch I used; I can send the database in question
if you want but I don't want to post it to the list.

Thanks,

Ed

[mdb-dev] AnonCVS instructions on front page

[Edward C. <ed...@ca...>]

I think the CVS instructions on http://mdbtools.sourceforge.net/ are
incorrect, instead of 

cvs -d:pserver:ano...@cv...:/cvsroot/mdbtools
login

it should be

cvs -d:pserver:ano...@cv...:/cvsroot/mdbtools login

as projects.sourceforge.net does not have a CVS server running.

Thanks!

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

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

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

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

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

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

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

-Camden

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

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

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

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

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

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

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

 -- Jeff Smith



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

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

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

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

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

-Camden Daily

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

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

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

Tried repairing your access database using the access repair utility?

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

Sam

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

[mdb-dev] Segmentation fault with a large table but not with small tables.

[Ron P. <ro...@sa...>]

Hi,
We are working with the present (24 Feb 2005) revision of mdbtools from =
the=20
CVS repository and are having a segmentation fault when trying to access =

large tables in a JET4 data file. Smaller tables in the same file can be =
accessed=20
without problems. The total size of the file is under 3 meg and the =
table in
question has 47 fields by about 1700 rows. We are able to reproduce the=20
problem in GDB as shown below by starting the "mdb-sql" utility and =
making=20
a simple query. We could provide the datafile if that would aid in =
debugging.
Below is a log of simple debug session with a failure when the program =
attempts
to print the first row of data from the query.=20

Alternatively, are there known limitations on table sizes that we should =
be aware=20
of? Further, are the clues about how to address this problem?
Thanks,
Ron=20


[ronp@aux util]$ gdb .libs/mdb-sql
GNU gdb 6.2-2mdk (Mandrakelinux)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you =
are
welcome to change it and/or distribute copies of it under certain =
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for =
details.
This GDB was configured as "i586-mandrake-linux-gnu"...Using host =
libthread_db library "/lib/tls/libthread_db.so.1".

(gdb) run st.mdb
Starting program: /home/ronp/mdb/mdbtools/src/util/.libs/mdb-sql st.mdb
1 =3D> select PNID from PN
2 =3D> go

+-----------+
|PNID       |
+-----------+

Program received signal SIGSEGV, Segmentation fault.
mdb_xfer_bound_data (mdb=3D0x804de08, start=3D0, col=3D0x8088ae8, =
len=3D0) at data.c:198
warning: Source file is more recent than executable.

198                             strcpy(col->bind_ptr, "");
(gdb) backtrace
#0  mdb_xfer_bound_data (mdb=3D0x804de08, start=3D0, col=3D0x8088ae8, =
len=3D0) at data.c:198
#1  0x4001cf1b in mdb_read_row (table=3D0x80877e0, row=3D0) at =
data.c:291
#2  0x4001d026 in mdb_fetch_row (table=3D0x80877e0) at data.c:387
#3  0x08049709 in dump_results_pp (sql=3D0x804d0d8) at mdb-sql.c:333
#4  0x08049dcd in main (argc=3D2, argv=3D0xbffff854) at mdb-sql.c:453
(gdb)

[mdb-dev] Column names getting cut off

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

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

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

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

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

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

Any help would be greatly appreciated.
-Camden Daily

RE: [mdb-dev] mdbtools-java: thanks!, status?, bug reports

[Calvin S. <cal...@ho...>]

>First of thanks to whomever did the Java port, I believe it was Calvin 
>Smith.

Yep it was me.  Thanks for the report.  good to hear someone is using this 
stuff
Bug 1)
  looks like a bug to me, just fixed it and checked it in

Bug 2)
  that bug may or may not have been in the C code.  I have found other 
places where the C code was wrong bug did not segfault.  can you try the 0.5 
version of the C code and see if it's also broke there?  keep in mind the C 
code may return the correct result but still be corrupting memory

Current plans are to sync the libmdb package to current cvs thereby picking 
up new feature and bug fixes.
JDBC driver works well for common cases so it tends to get less attention 
until someone like yourself reports the bug and / or offers a patch

Thanks again

----Original Message Follows----

First of thanks to whomever did the Java port, I believe it was Calvin 
Smith.  I need to read data from an mdb file on a Linux system via a Java 
servlet, and this project (almost) allowed me to do that.  I first used the 
libmdb package ala mdb_export, but I found the test code that does 
DriverManager.getConnection("jdbc:mdbtools:" + filename), which 
worked well.  Even though very little of the java.sql interfaces are 
implemented, we have Statement.executeQuery and ResultSet.getString, which 
are sufficient for my purposes.  Thanks again!

Other posts indicate that the Java port is a bit out-of-date, so perhaps the 
memo bug I describe below has been fixed in the C version.  From the libmdb 
code, it looks like some manual intervention is required to turn the C into 
Java, so perhaps this is why.

I am not part of the mdbtools team and have not participated in any such 
project, so I will describe two bugs I found and apologize for not fixing 
them.

1) Java bug (crucial, but trivial): in DataResultSet.getString(String), the 
method loops through the column names to get the index to call 
DataResultSet.getString(int), which does the real work.  
DataResultSet.getString(int) correctly accounts for the fact that 
ResultSet.getXXX(int) method number the columns from 1, as does SQL.  
However, DataResultSet.getString(String) does not account for the offset.  
Line 168 "return getString(i);" in the for loop should be return 
"getString(i + 1);".  (I'm not sure what the plans are for the 
Java wrappers, but obviously a table from column names to indices in 
DataResultSet would be better.)

2) I'm getting various index out of bounds errors from 
mdbtools.libmdb.Data.mdb_memo_to_string that are preventing me from reading 
tables that have a column of type "memo".  I can't even query the 
other columns because the current implementation reads the entire tale into 
memory, no matter what columns are in the query (right?).  I'm getting 
negative values for the string length and a value > 4096 for row_start, 
which is used as an index into MdbHandle.page_buf.



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
mdbtools-dev mailing list
mdb...@li...
https://lists.sourceforge.net/lists/listinfo/mdbtools-dev

Re: [mdb-dev] mdbtools-java: thanks!, status?, bug reports

[Mike P. <mj...@fi...>]

> 2) I'm getting various index out of bounds errors from 
> mdbtools.libmdb.Data.mdb_memo_to_string that are preventing me from 
> reading tables that have a column of type "memo".  I can't even query 
> the other columns because the current implementation reads the entire 
> tale into memory, no matter what columns are in the query (right?).  I'm 
> getting negative values for the string length and a value > 4096 for 
> row_start, which is used as an index into MdbHandle.page_buf.

Randomly, I wonder if this is related to my PHP->ODBC->mdbtools problems 
with memo fields...

-- 
Cheers,

Mike

mj...@fi...                             http://www.filmsat59.com
Films at 59 Ltd, 59 Cotham Hill, Bristol. BS6 6JR. UK +44 117 906 4300

[mdb-dev] mdbtools-java: thanks!, status?, bug reports

[Caleb D. <dr...@cs...>]

First of thanks to whomever did the Java port, I believe it was Calvin 
Smith.  I need to read data from an mdb file on a Linux system via a 
Java servlet, and this project (almost) allowed me to do that.  I first 
used the libmdb package ala mdb_export, but I found the test code that 
does DriverManager.getConnection("jdbc:mdbtools:" + filename), which 
worked well.  Even though very little of the java.sql interfaces are 
implemented, we have Statement.executeQuery and ResultSet.getString, 
which are sufficient for my purposes.  Thanks again!

Other posts indicate that the Java port is a bit out-of-date, so perhaps 
the memo bug I describe below has been fixed in the C version.  From the 
libmdb code, it looks like some manual intervention is required to turn 
the C into Java, so perhaps this is why.

I am not part of the mdbtools team and have not participated in any such 
project, so I will describe two bugs I found and apologize for not 
fixing them.

1) Java bug (crucial, but trivial): in DataResultSet.getString(String), 
the method loops through the column names to get the index to call 
DataResultSet.getString(int), which does the real work.  
DataResultSet.getString(int) correctly accounts for the fact that 
ResultSet.getXXX(int) method number the columns from 1, as does SQL.  
However, DataResultSet.getString(String) does not account for the 
offset.  Line 168 "return getString(i);" in the for loop should be 
return "getString(i + 1);".  (I'm not sure what the plans are for the 
Java wrappers, but obviously a table from column names to indices in 
DataResultSet would be better.)

2) I'm getting various index out of bounds errors from 
mdbtools.libmdb.Data.mdb_memo_to_string that are preventing me from 
reading tables that have a column of type "memo".  I can't even query 
the other columns because the current implementation reads the entire 
tale into memory, no matter what columns are in the query (right?).  I'm 
getting negative values for the string length and a value > 4096 for 
row_start, which is used as an index into MdbHandle.page_buf.

Re: [mdb-dev] mdb-sql - problem with "_" in table name

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

--- Radek   Tomá¹ek <rad...@ce...> wrote:
> echo "Select * from Alloc_NSE_TNE" | mdb-sql test.mdb   ...  error: Error at line :
> syntax error near _   Couldn't parse SQL

You must be using an old version of mdbtools.  I would suggest you go to 0.6pre1 or to
what is in CVS.

 -- Jeff Smith




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

[mdb-dev] mdb-sql - problem with "_" in table name

[Radek <rad...@ce...>]

Hi all,
I have MSAccess database with tables which contain the "_" char in name.

When I try run following commands I get an error.
echo "Select * from Alloc_NSE_TNE" | mdb-sql test.mdb   ...  error: Error at line : syntax error near _   Couldn't parse SQL
echo "Select * from 'Alloc_NSE_TNE'" | mdb-sql test.mdb   ...  error: Error at line : syntax error near Alloc_NSE_TNE   Couldn't parse SQL
and another command with the similar syntax are wrong.

But when I write  echo "Select * from Test" | mdb-sql test.mdb  command is OK. (In table name is not "_" char)

Please help, how write commands with "_" in table name.

Thanks
Radek

[mdb-dev] mdb-sql - problem with "_" in table name

[<r.t...@ct...>]

Hi all,
I have MSAccess database with tables which contain the "_" char in name.

When I try run following commands I get an error.
echo "Select * from Alloc_NSE_TNE" | mdb-sql test.mdb   ...  error: =
Error at line : syntax error near _   Couldn't parse SQL
echo "Select * from 'Alloc_NSE_TNE'" | mdb-sql test.mdb   ...  error: =
Error at line : syntax error near Alloc_NSE_TNE   Couldn't parse SQL
and another command with the similar syntax are wrong.

But when I write  echo "Select * from Test" | mdb-sql test.mdb  command =
is OK. (In table name is not "_" char)

Please help, how write commands with "_" in table name.

Thanks
Radek

Re: [mdb-dev] OS X compiling...

[Neil T. <nt...@ea...>]

Are you using stable or unstable?

At 12:46 PM -0700 2/11/05, michael geary wrote:
>fink chokes on glib2 on my machine. It says it needs to install 17 
>dependencies first, and then dies on the gmp package, long before it 
>gets to glib2... :c(
>
>I don't believe that gmp is _really_ needed for glib2. Any ideas on 
>how I can override fink's dependency mechanism?
>
>thanks,
>
>michael geary
>
>
>On Feb 11, 2005, at 3:04 AM, Neil Tiffin wrote:
>
>>glib and glib2 both install fine using fink.
>>
>>http://fink.sourceforge.net/index.php
>>
>>Neil

Re: [mdb-dev] Internationalisation of the command line tools

[<pa...@ti...>]

Jeff Smith wrote:

>--- "Pedro A. Aranda Guti=E9rrez" <pa...@ti...> wrote:
>+-----------+--------------------------------------------------+----=
----------------------------------------------+
> =20
>
>>|IdDirector |Apellidos                                        =20
>>|Nombre                            |
>>
>>   =20
>>
>+-----------+--------------------------------------------------+----=
----------------------------------------------+
> =20
>
>>|96         |Previn                                           =20
>>|Andr=C3=A9                            |
>>
>>   =20
>>
>+-----------+--------------------------------------------------+----=
----------------------------------------------+
> =20
>
>>1 Row retrieved
>>
>>The column 'Nombre' should show Andr=E9. Is there someone working o=
n this?
>>   =20
>>
>
>It is showing Andr=E9 -- in UTF8.  To get it to show up in another e=
ncoding,
>you need to set the environment variable MDB_ICONV to the encoding y=
ou want.
>Run 'iconv -l' to see the available encodings.  Most people that nee=
d it
>changed would want ISO-8859-1.
> =20
>
Thanks a lot. There is a Spanish proverb: "You'll never go to sleep=
=20
without having learnt
something new" :-)

>>Then, I'd also like to point out that mdb-sql is extremely interest=
ing=20
>>for many quick
>>prototyping applications, but only if it can be used as a coprocess=
. For=20
>>that you need
>>to add an
>>    fflush(stdout);
>>after every
>>    fprintf(stdout,"\n");
>>
>>I know it sounds tedious, but the application for this is really=
=20
>>_great_. I could provide
>>a patch for adding this.
>>   =20
>>
>
>What information can you give on how you are using it?  What are you=
 doing
>that libmdbsql cannot provide?
> =20
>
I didn't have the time to go through libmdbsql and had mdb-sql runnin=
g.=20
So I made this
trivial patch and now I am able to write C programs (using tcc I don'=
t=20
even need to compile
them to do the tests) which access my MDB files via mdb-sql. This can=
=20
also apply for people
you might want to access MDB using AWK or other scripting languages.=
=20
This fflush() over-
comes the UNIX limitation of not flushing stdout after a "\n" if stdo=
ut=20
is connected to a pipe.

It's not that you do something you wouldn't be able to do... it's mor=
e=20
the convinience of having
a running program and 'connecting' it to other tools. Isn't this what=
 we=20
all love in **IX OS's ?? :-)

Regards,

--=20
Pedro Andr=E9s Aranda Guti=E9rrez
Telef=F3nica  I+D          IP Network Access Technologies
Consultant                           mailto:pa...@ti...
C./ Emilio Vargas, 6                Tlf +34-91 337 4702
E-28043 Madrid, Spain               FAX +34-91 337 4502

Fragen sind nicht da, um beantwortet zu werden.
Fragen sind da, um gestellt zu werden  - Georg Kreisler

Re: [mdb-dev] Internationalisation of the command line tools

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

--- "Pedro A. Aranda Gutiérrez" <pa...@ti...> wrote:
+-----------+--------------------------------------------------+--------------------------------------------------+
> |IdDirector |Apellidos                                         
> |Nombre                            |
>
+-----------+--------------------------------------------------+--------------------------------------------------+
> |96         |Previn                                            
> |André                            |
>
+-----------+--------------------------------------------------+--------------------------------------------------+
> 1 Row retrieved
> 
> The column 'Nombre' should show André. Is there someone working on this?

It is showing André -- in UTF8.  To get it to show up in another encoding,
you need to set the environment variable MDB_ICONV to the encoding you want.
Run 'iconv -l' to see the available encodings.  Most people that need it
changed would want ISO-8859-1.

> Then, I'd also like to point out that mdb-sql is extremely interesting 
> for many quick
> prototyping applications, but only if it can be used as a coprocess. For 
> that you need
> to add an
>     fflush(stdout);
> after every
>     fprintf(stdout,"\n");
> 
> I know it sounds tedious, but the application for this is really 
> _great_. I could provide
> a patch for adding this.

What information can you give on how you are using it?  What are you doing
that libmdbsql cannot provide?

 -- Jeff Smith

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Re: [mdb-dev] SEGV with > 255 character MEMO fields in PHP/ODBC

[Mike P. <mj...@fi...>]

Hi Brian,

> Just out of curiousity, what happens if you run it through ODBC (isql)
> without PHP?

Showing what a neophyte I am, I didn't know about that!

Tried that, and it runs through fine, which is a shame, as it would have been 
nice to eliminate PHP!

I've attached a test DB, PHP script and odbc.ini .... I'll keep on plugging 
through today on and off to see if I can get any more clues.

-- 

Cheers,

Mike

mj...@fi...                                 http://www.filmsat59.com
Films at 59 Ltd, 59 Cotham Hill, Bristol. BS6 6JR ENGLAND +44 117 906 4300