To try out the ODBC driver with my application, I tried to use OpenOffice 2.0. It opens
the connection and displays the tables but gives a SQL error when I try to access a table.

I see from a 2 year old message here that OpenOffice used an unsupported SQL statement.

Any changes in this in the last 2 years?

I turned on tracing but the resulting SQL.log file is empty. Any idea why I didn't get any
trace information?


Tom

Tom,

<< To try out the ODBC driver with my application, I tried to use OpenOffice
2.0. It opens the connection and displays the tables but gives a SQL error
when I try to access a table.

I see from a 2 year old message here that OpenOffice used an unsupported
SQL statement.

Any changes in this in the last 2 years? >>

Yep, the latest 4.x ODBC driver supports absolute fetching now.  What is the
error message that you're getting ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

The error message is syntax error in SQL expression.

Clicking More, gives:


SQL Status: HY000
Error code: 1000

SELECT * FROM "D:"\"U\UV\ProdHistDB\part_tbl"

parse error, expecting `$', Invalid symbol

The path looks suspect to me. It should be "d:\u\uv\prodhistdb\part_tbl"

Tom

Tom,

<< The error message is syntax error in SQL expression.

Clicking More, gives:

SQL Status: HY000
Error code: 1000

SELECT * FROM "D:"\"U\UV\ProdHistDB\part_tbl"

parse error, expecting `$', Invalid symbol

The path looks suspect to me. It should be "d:\u\uv\prodhistdb\part_tbl" >>

Are you getting a DBISAM error code and message ?  This doesn't sound like
any error that we would issue.  Our SQL parser never expects to see the '$'
token for any type of identifier, etc.

--
Tim Young
Elevate Software
www.elevatesoft.com

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote:

Are you getting a DBISAM error code and message ?  This doesn't sound like
any error that we would issue.  Our SQL parser never expects to see the '$'
token for any type of identifier, etc.


Tim,

The quoted error message is from OpenOffice. Not a peep from the ODBC driver. And my
attempts to use the ODBC driver trace produced nothing but an empty sql.log file. It would
probably help if the ODBC trace could be made to work. Any idea what might be wrong there?

Since the path in the error message is that of the table, OpenOffice must be getting it
from the ODBC driver. So it is making some kind of connection.

This is the first time I've ever tried doing anything with ODBC. So don't assume I'm not
making a very basic mistake here.

Tom

Tom,

<< The quoted error message is from OpenOffice. Not a peep from the ODBC
driver. And my attempts to use the ODBC driver trace produced nothing but an
empty sql.log file. It would probably help if the ODBC trace could be made
to work. Any idea what might be wrong there? >>

You have to make sure that a) all applications accessing ODBC are closed and
b) that you stop the tracing via the ODBC Administrator before you try to
look at the log file.  Other than that, I'm not sure what the problem is.

<< Since the path in the error message is that of the table, OpenOffice must
be getting it from the ODBC driver. So it is making some kind of connection.
>>

True.  However, if the error was coming from our ODBC driver, then you would
see "[Elevate Software][DBISAM]" in the error message.  If the error isn't
coming from our ODBC driver, then I'm afraid I can't do much about it.

--
Tim Young
Elevate Software
www.elevatesoft.com