We develop a database engine for Windows called ElevateDB, and one of our
customers contacted us regarding using OpenOffice with the ODBC driver that
we provide for the ElevateDB. The problem is that we can get OpenOffice to
connect, list tables, etc. just fine, but viewing the tables in the grid via
the Open right-click menu results in less-than-accurate results. Sometimes
there are blank rows, and sometimes there are missing rows, etc., but not
with all tables. Some tables display just fine. There really isn't any
rhyme or reason to it.
What I am looking for is access to the developer(s) that is/are responsible
for the ODBC connectivity and how it relates to the grid view of tables in
OpenOffice. I need to find out what OpenOffice expects in terms of the
SQLFetchScroll calls to the ODBC driver, because right now our driver is
obviously not responding in a way that OpenOffice expects it to. However,
our driver is written *exactly* to the ODBC 3.x spec for the SQLFetchScroll
behavior, and works just fine with VB in terms of scrollable, bi-directional
cursors (it supports first, last, next, prior, relative, and bookmarks).
For example, one thing that I've found is that OpenOffice ignores the fact
that our driver tells it that it doesn't support absolute fetches, yet it
goes ahead and calls SQLFetchScroll with SQL_FETCH_ABSOLUTE as the
FetchOrientation.
I've tried looking at the OpenOffice source code to figure out what is going
on, but I can't find the applicable grid code as it relates to the
navigation and population of the rows.
Thanks,
Tim Young
Elevate Software
www.elevatesoft.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
