Re: Linking Access f/e to Access b/e via ODBC

Hi, Nicola.

> Is it possible then to create an ODBC connection to use the ISAM driver
> rather than the Access one offered to me when I create the DSN?

If I understand your question correctly, the ISAM driver for Jet _is_ what
you're getting when you create the DSN for an Access database file. To
clarify, the ODBC Data Source Administrator can create the DSN to the Access
database file for you, but it will always use (or, as you put it, offer) the
built-in ISAM driver for Jet, because that's the best driver for the
connection to Jet's tables.

> Unless anybody has any better ideas for allowing the database to be
> portable?

There are many ways to connect to the back end, such as with linked tables,
DSN's or DSN-less connections. I'd suggest posting a new question yourself
so that you get a wider audience suggesting better alternatives than just
the people interested in reading about ODBC links to Access tables, which
isn't possible.

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)


"Nicola Jones" <NicolaJones@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:ECD8B0A4-F832-406B-9E1B-3FD9A425504E@xxxxxxxxxxxxxxxx
>I am trying to do the same thing because I don't want to have to relink all
> the tables everytime I change the databases location on the network.
>
> Is it possible then to create an ODBC connection to use the ISAM driver
> rather than the Access one offered to me when I create the DSN?
>
> Unless anybody has any better ideas for allowing the database to be
> portable? I will always have the link ed access database in the same
> directory as the master one, but when I create a "normal" link to the
> other
> access database it seems to hard code under the scenes either the drive
> letter and folder or the unc path, if that is how I obtain the link.
>
> "'69 Camaro" wrote:
>
>> Hi.
>>
>> > Does anyone know if it is possible (and how) to configure an Access f/e
>> > as
>> > above to enable running of b/e queries as a database server
>> > (client/server)
>> > instead of file server? I get the following error when attempting to
>> > 'Link'
>> > to Access ODBC connection:
>>
>> You cannot use an ODBC (Open DataBase Connectivity) driver for Microsoft
>> Access tables. You must use the built-in ISAM (Indexed Sequential Access
>> Method) driver for Jet in order to connect to the tables in the external
>> Access database. For more information on MDAC (Microsoft Data Access
>> Components), please see the following Web page:
>>
>> http://safariexamples.informit.com/0789722534/3rdparty/Microsoft/PROJ2000/SYSTEM/MDACRDME.HTM#odbc
>>
>> HTH.
>>
>> Gunny
>>
>> See http://www.QBuilt.com for all your database needs.
>> See http://www.Access.QBuilt.com for Microsoft Access tips.
>>
>> (Please remove ZERO_SPAM from my reply E-mail address, so that a message
>> will be forwarded to me.)
>>
>> - - -
>> When you see correct answers to your question posted in Microsoft's
>> Online
>> Community, please sign in to the Community and mark these posts as
>> "Answers,"
>> so that all may benefit by filtering on "Answered questions" and quickly
>> finding the right answers to similar questions. Remember that the first
>> and
>> best answers are often given to those who have a history of rewarding the
>> contributors who have taken the time to answer questions correctly.
>>
>>
>> "NJS" wrote:
>>
>> > Does anyone know if it is possible (and how) to configure an Access f/e
>> > as
>> > above to enable running of b/e queries as a database server
>> > (client/server)
>> > instead of file server? I get the following error when attempting to
>> > 'Link'
>> > to Access ODBC connection:
>> >
>> > You cannot use ODBC to import from, export to, or link an external
>> > Microsoft
>> > Jet or ISAM database table to your database. (Error 3423)
>> > You are attempting to link, import data from, or export data to either
>> > an
>> > external Microsoft Jet table or an external ISAM database table (for
>> > example,
>> > dBASE, Microsoft® FoxPro®, Paradox, or Btrieve), but you have selected
>> > <SQL
>> > Database> as the data source. You must select the appropriate data
>> > source for
>> > the data you are attempting to link.
>> >
>> > thank you


.

Relevant Pages

  • Re: [VW 7.3.1] ODBCConnection
    ... I played around with a few combinations on the connection string and ... with a trusted SQL Server connection. ... there are differences for database connects. ... > any database specific odbc drivers. ...
    (comp.lang.smalltalk)
  • Re: Ada DB bindings and APQ
    ... >>I didn't like the use of handles for database objects. ... > will ensure that the connection will not go away until at least one query ... > things which can be made with a connection. ... That is different to ODBC. ...
    (comp.lang.ada)
  • Re: Mailmerge using a secure database
    ... Database does not have a long path name. ... When I tried re-opening my mail merge documents I get an error message ... Do you need or want specifically to connect with ODBC? ... likely to run into problems where Word truncates the connection string ...
    (microsoft.public.word.mailmerge.fields)
  • Re: Trusted Connection
    ... HOWEVER, for one of my users, I will create an ODBC DSN ... for my test database ON THEIR COMPUTER, ... So, when I set up the ODBC DSN connection for this user, ... >> Our SQL Server was set up NOT by me, ...
    (microsoft.public.sqlserver.security)
  • Re: Data Source Lost When Merge From Access to Word
    ... DDE was the default connection method and ODBC was the alternative as far as Access/Jet sources were concerned. ... In Word 2003, OLE DB is the default, but unfortunately when you have selected your database, Word does not display the Access tables that are linked to ODBC data sources. ... create one query in your Access database for each linked table you want to use, with SELECT * FROM, and use that as the data source. ...
    (microsoft.public.word.mailmerge.fields)