Local database with ODBC interface

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am trying to create a local copy of an Oracle database to be used by an
antiquated application. It communicates via an ODBC interface. I'm thinking
that I can re-create the tables locally (through Access), and setup some sort
of ODBC scheme. First off, is this feasible? Secondly, how would I go about
doing it? I apologize for the open-ended nature of these questions. If you
can point me in the direction of literature that may help me, that would be
great also.
 
I downloaded the ODBC drivers (version 10.1.0.4.0 - not sure if this is the
correct ones), and ran the install utility. It added some .class files to
the install directory. I then tried to link using File > Get External Data >
Link, but am not sure how to complete the next phase of this process. What
should I do next, and what should I expect to see?

Thanks,
Todd
 
If the antiquated application used an ODBC library, then
yes, it is possible.

Administrative Tools, Data Sources (ODBC),
Drivers,
Microsoft Access Driver (*.mdb)

If the antiquated application used DAO, then possibly,
maybe not.

DAO will only connect to an MDB database using the internal
jet library. If the user interface forces you to provide
an ODBC connection, for example a DSN name, then you won't
be able to enter the path to the MDB.

I can't see your application, or tell you which library
it uses, but you can try it and see.

You don't need to create the correct database first. I'm
sure you will get a different error if you can't connect
than you will get if all of the tables are missing.

(david)
 
The driver name used by the Data Source in question is "Oracle 73 Ver 2.5".
I've never done this type of linking before, so please share any subtleties
in this process. Thanks.
 
The question is, how does the antiquated application
know what to link to? Is there a place where you type in
a DSN? If so create a new Access DSN and see what
the error message is.

(david)
 
When the utility (the term "application" gives it more prestige than is
warranted) is launched, it asks for a login name and password - the current
system must use some sort of DSN. Which driver should I select from the
"Create New Data Source" window? Thanks.
 
Microsoft Access Driver (*.mdb)

The login name and password window is normally an ODBC window. (It is bad
design to create your own window and pass the values through to odbc).

If the login window does not give you the option to choose a DSN or
connection, then the system must have a hardcoded dsn or connection name. If
you can't select a DSN, you will have to try to work out the DSN name, so
that you can re-name it, and use your own DSN.

(david)
 
Back
Top