Could the new database stored procedures interfere with older OLE DB drivers?

[Jeffrey P. Silverstone]

I notice that on the database that I had the beta stored procedures on, I do
not see the tables listed in VS05 database connections (using an OLE DB
driver). I see views and stored procedures, however.

When I look at a connection to a database that has no stored procedures, I
see the tables. Other than noting that the connection string reads,
"Provider=Sybase.ASEOLEDBProvider.2", I don't know how to be sure which
version of the OLE DB driver it is using.

-- Jeffrey

[Jeffrey P. Silverstone]

I can add that the OLE DB driver that I am using seems to be 2.70.0.53 . I
have now verified the problem on a second client machine. Version 12.5.1.548
does not seem to have this problem. I use the older driver because I do not
have permissions to install the stored procedures (it took a month to get
the beta procedures installed on my development-only machine). Nonetheless,
it is a bug in the new stored procedures if they break existing, working,
clients.

-- Jeffrey

"Jeffrey P. Silverstone" <jps-...@margreta.com> wrote in message
news:468ea0a7@forums-1-dub...

[Paul]

Hi Jeffrey,

The new provider , sybadroledb.dll (ASEOLEDB) uses totally different
procedures then
the older OEM Provider, SYDAASE.DLL, Sybase.ASEOLEDBProvider). There should
be no conflicts.

What beta do you refer to?

-Paul

"Jeffrey P. Silverstone" <j...@nospamplease.com> wrote in message
news:46922bfe@forums-1-dub...

[Jeffrey P. Silverstone]

The asp.net 2.0 beta and its stored procedures. Note that I never explicitly
loaded in stored procedures for the old driver. My inability to load global
stored procedures without DBA involvement is why I stuck with the old
drivers.

-- Jeffrey

"Paul" <Pa...@sybase.com> wrote in message news:4693fdca$1@forums-1-dub...