On Sat, Jun 9, 2012 at 12:30 PM, Confused <[email protected]> wrote:
> Forgot to mention....
> Was able to make the datasource using the 32-bit control panel applet, but
> BD does not see it.
> When I try to run a query against it, I get:
> The Datasource XXX could not be found or was invalid.
> javax.naming.NameNotFoundException: Name XXX is not bound in this Context
>
I kind of doubt you'll have success with the 32-bit ODBC stuff on 64-bit
Windows. As I said before it's just not a scenario I considered when
building the admin console so I'm not surprised it doesn't work.
That said, and bear in mind I'm completely ignorant about this level of
detail on Windows, can you *not* have everything be 64-bit somehow? For
example have you tried creating a datasource in Windows (meaning in the
Windows control panel, not in OpenBD) to something other than Access and
seeing if OpenBD auto-detects that datasource? Is there no 64-bit ODBC?
If you must use Access you will probably find a much shorter path to
success by trying the JDBC-ODBC bridge driver directly and not configuring
the datasource in Windows itself. I'm pretty sure the JDBC-ODBC bridge
driver ships with Java still, so configure a datasource of type "Other" and
the driver class would be sun.jdbc.odbc.JdbcOdbcDriver
JDBC URL syntax should be something like this:
jdbc:odbc:Driver={Microsoft Access Driver
(*.mdb)};DBQ=c:/path/to/accessfile.mdb
It might take some experimentation but I think that path will be more
fruitful than trying to configure via Windows and have OpenBD see it.
--
Matthew Woodward
[email protected]
http://blog.mattwoodward.com
identi.ca / Twitter: @mpwoodward
Please do not send me proprietary file formats such as Word, PowerPoint,
etc. as attachments.
http://www.gnu.org/philosophy/no-word-attachments.html
--
online documentation: http://openbd.org/manual/
http://groups.google.com/group/openbd?hl=en
