Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.misc -> Re: SQL*Net 1 ==> SQL*Net 2

Re: SQL*Net 1 ==> SQL*Net 2

From: Kevin P. Fleming <kfleming_at_access-laserpress.com>
Date: 1998/01/23
Message-ID: <34C91445.ED14DDB3@access-laserpress.com>#1/1

No, you can't do that, but you can certainly update the table attachments in Access to use the new connect string format. This can be using either Access' Linked Table Manager or from Access Basic code, your choice.

Dan Hopkins wrote:
>
> I hope someone out there can explain this to me : (I'm an Oracle / SQLNet
> newbie :( )
>
> We've been using the 16-bit version of Microsoft Access to ..er.... access
> an Oracle database.
> We're now attempting the move to Access 97 and the 32 bit version of ODBC
> (SQLNet 2.3, Oracle 7.3.3)
>
> The SQL*Net connect string using the 16-bit ODBC consisted of
> t:auth:administration
> SQL*Net 2 apparently doesn't need the t:auth: and will connect perfectly
> using just
> administration as the connect string.
>
> Unfortunately, the Access databases we used all consist of attached tables
> with the connect
> string embedded in the table properties. Once converted to Access 97, the
> linked tables, forms etc
> refuse to connect.
>
> Is there any way I can get SQL*Net 2 to accept the same connect string as
> the old 16-bit version ?
>
> Any help / suggestions appreciated.
> Regards,
>
> --------------------------------------------
> Dan Hopkins
> Systems Admin & Development
> UK Online Ltd.
> email: dan_at_ukonline.net
> --------------------------------------------
Received on Fri Jan 23 1998 - 00:00:00 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US