ODBC driver for W95

We have a lot of W95 clients that can't be upgraded. I want to use SQL CLR s
o
I need to use SQL 2005. Is there an ODBC driver for W95? I've tried MDAC 2.8
but without success (installation fails on W95).
--
SteveHi
Windows 95 and Windows 98 are out of extended support. No new MDAC or SQL
Server Native Client components for SQL Server 2005 have been developed for
those platforms.
http://support.microsoft.com/lifecycle/?p1=7864
http://support.microsoft.com/lifecycle/?p1=6513
Regards
--
Regards
Michel Epprecht [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
"SteveR" <SteveR@.discussions.microsoft.com> wrote in message
news:DEF89788-65DB-42C5-A2FC-9D3A62AE5430@.microsoft.com...
> We have a lot of W95 clients that can't be upgraded. I want to use SQL CLR
> so
> I need to use SQL 2005. Is there an ODBC driver for W95? I've tried MDAC
> 2.8
> but without success (installation fails on W95).
> --
> Steve

ODBC Connection Fails from cluster node

I had a stand alone sql server that I upgraded to a cluster. I have an odbc connection called my_connection. The odbc test works fine. When I call the dsn from a php script it fails with this message:

Warning: odbc_connect(): SQL error: [Microsoft][ODBC SQL Server Driver][DBNETLIB
]SQL Server does not exist or access denied., SQL state 08001 in SQLConnect in D
:\storage\test.php on line 3
Could not connect to my_connection!

This same script works fine from any other computer. Is there an issue with connecting to a virtual server from the node via ODBC? Is there something I need to change in the client protocols?

Thanks in advance.

What's your connection string? The server name must have been changed (from the machine name to cluster network name resource name). Have you changed it in your conn string? Is it a default instance and named instance?|||

I also like to add that when I run Component Checker 2.0 I get

The following product releases were matched:

UNKNOWN

I'm wondering if this is the culprit.

|||

Its a system dsn, with SQL Server driver. The server is my virtual server name, and it uses sql authentication.

Does that answer your question? My odbc connection by itself works fine, but it doesn't when called from another app.

|||hmm, If you are able to connect when you test the DSN but fails in your app, I'm not sure what I can do. There are probably some issue with your app. I hope you test your app and DSN under same account.|||

This issue appears to be MDAC. Uninstalling and reinstalling SQL to enable clustering must have caused the problem.

What I did to figure this out was change the connection from dsn to dsn-less and it worked.

ODBC connection - lost tables

I have a SQL Server database that I connect a front end to using an ODBC connection. Our LAN folks upgraded the server recently and now I can no longer see any of the tables through the ODBC connection that the user used for login has permission in SQL Server Enterprise Manager to see - throught the ODBC connection the user can only see things like:

dbo.spt_datatype_info
dbo.spt_datatype_info_ext
dbo.spt_fallback_db
dbo.spt_fallback_dev
dbo.spt_fallback_usg
.
.
.
INFORMATION_SCHEMA.CHECK_CONSTRAINTS
INFORMATION_SCHEMA.COLUMN_DOMAIN_USAGE
etc.

I've tried deleting the user for the connection and re-establishing it with owner permissions. I've tried deleting the dsn and re-establishing that as well but nothing so far.

Please help!!!Sounds like your default database for the user is master...

is it?

Can you edit the connection and look?|||Do you mean throught the ODBC Administrator or through SQL Server Enterprise manager?|||If you're connecting a client to sql server...it'll be on the client...

And since you're seeing the INFORMATION_SCHEMA views...they live in master...

You'll need to change the default database to where your data is, I think (only sometimes, mind you)|||I'm not sure how to change the master on my client machine - could you walk me through that?

I sit next to some Oracle folks and from what they know of SQL Server there is a master dbase with sub dbases - the one I'm accessing being a sub dbase. The master dbase peers into the subs through views. It sounds to them as though the master dbase doesn't have the proper permission to see all the tables or perhaps the view is incorrect. Is this close to what you are talking about?|||You control the default database when you create the dsn - look at your dsn settings for default database (it defaults to master).|||Hold on...don't listen to the Oracle guys...different world

been there...

there are no "Sub" databases..there are instances (a word they should know) in sql2k...

Hold on...I'm on win2k ok?

go to start>Settings>control panel

2xclick on data sources

Find your dsn...2x click on or configure...

Go 2 or 3 clicks on NEXT...you should see the default db...

btw...how do you distribute the odbc to the clients?|||You are the man!!! I found the default database and that was it. Thank you very much!

For those of you reading and don't know where that is on Windows 2K and XP open your ODBC Administrator -> add a User DSN -> select a driver (in this case SQL) -> type in a name and a server, description is optional -> set up authentication as needed -> at the top of the next screen is where you change your default database -> leave default settings on the next screen -> test and you're done.|||Great...and good luck...

But how do you plan to distribute the connection?|||Actually what I have is a document in a shared folder that walks the user through the ODBC setup. All users login to the dbase with the same user info and their data access is controlled through the front end. Not the best solution but the data isn't sensative and the cost was zero since me and another guy set it up in-house.

Thanks again!sql