That is exactly the answer... whatever you've used ODBC&SQLNet on your
client WinNT machine should be installed to the Citrix server... (system
DSN)
"Howard J. Rogers" <howardjr_at_www.com> wrote in message
news:3bba252a_at_news.iprimus.com.au...
> Probably out of my league here, but what happens if you install the Oracle
> Client software on the terminal server itself? That should allow the
> terminal host to establish ODBC connections, and all terminal sessions
> should then be able to use them.
>
> Regards
> HJR
>
> "pher" <no.spam_at_plea.se> wrote in message
> news:0enjrt0f42r3kbsj9fscnss8t6e7b8h68b_at_4ax.com...
> > >
> > >You probably don't want to use the Citrix driver, but the Oracle ODBC
> > >driver instead. This one goes directly to the database. It must first
> > >be
> > >installed on the client. To see if you have it open your control
> > >panel and go to the ODBC data sources applet. Then click on the
> > >drivers tab and see if Oracle is listed there. If not, get the client
> > >CD and install it.
> >
> > I'm not sure that it's what I want:
> > my users use Wyse terminals to connect to Terminal Server. They have
> > no PCs. They open an Access database that should contain tables linked
> > to an Oracle db. Problem : I can only link via ODBC, but problem:
> > there is no Oracle ODBC driver on Terminal Server.
> > Is there one ?
> > Note: connecting to the Oracle DB from my NT workstation via ODBC or
> > SQL*Net is not a problem ! My problem occurs when I want to put the
> > Access database on Terminal Server.
> > Pierrot
>
>
Received on Wed Oct 03 2001 - 06:05:54 CDT
