"Boknaai" wrote:

> Thanks John, I tried using an IDS file, but users get the same error still
>
> "John Bell" wrote:
>
> > Hi
> >
> > I am not a sybase user, but using a DSN would mean that you have ODBC on top
> > of OLEDB connection. I would therefore looks to use OLEDB directly. The
> > following site http://www.connectionstrings.com/ talks about possibly using a
> > .IDS file for ASE and other things that are needed.
> >
> > John
> >
> > "Boknaai" wrote:
> >
> > > Hi!
> > >
> > > I have written a stored procedure that uses a distributed query that looks
> > > like the following:
> > >
> > > SELECT Code, ShortName
> > > FROM OPENQUERY(LINKED1, 'SELECT Code,ShortName FROM dbo.Client') Client
> > >
> > > LINKED1 refers to a system DSN on the server that is link to a Sybase
> > > database.
> > >
> > > I can run this stored procedure and use it in my code to my hearts' content,
> > > but as soon as anybody else (ie permited users on the database) tries to use
> > > it, they get an error saying "System.Data.SqlClient.SqlException: Could not
> > > create an instance of OLE DB provider 'Sybase.ASEOLEDBProvider'."
> > >
> > > The Sybase database requires a username and password to logon to it, which
> > > is different to the windows credentials that users use to get onto my SQL
> > > server database. So in the Linked Server properties -> security tab, I have
> > > checked the "Be Made With This Security Context" button and filled in a valid
> > > username and password for the Sybase database. But this seems to make no
> > > difference.
> > >
> > > The fact that I can run this stored procedure means that the Sybase database
> > > accepts distributed queries so it must be a security issue of sorts. I
> > > installed the instance of SQL server so I obviously have full administratice
> > > rights.
> > >
> > > Any help/suggestions would be much appreciated