I'm running an access application on my local server (SQL Server 2000)
On my win 2000 it worked perfectly.
On my win XP, I always get this error message :
3151: ODBC--Connection to 'MyODBC' Failed.

sp_provider_types_rowset and some other stored procedures keep being
executed
We recently experienced a very interesting problem. When connecting to SQL
Server 2000 (SP4) using ADO, after the recordset is retrieved,  we can see

We've just stumbled on a 1.0 version incompatibility with the JDBC specs.
Problem: A table with SMALLINT column. According to JDBC specs version 3.0
(p.B-179) and 4.0 (p.221)), the value should be converted to Integer type.
Unfortunatelly we get a Short object :(

When I try to connect to an instance of SQL 2005 in Management Studio on my
laptop, I get the following error message:
An error has occurred while establishing a connection to the server.  When
connecting to SQL Server 2005, this failure may be caused by the fact that

I have sql 2k5 installed (developer ed) on my advanced server 2000.  It
allows remote connections.  I'm trying to connect using sql authentication.
The server is not a member of a domain.
I try to connect from an XP system using an IP number, sql user and

I created ASP.NET 2.0 web application that uses SQL Server 2000 database and
it works perfectly when website and Sql server were on  local machine.
Then I installed application on production server. Database is placed on
another server.

Im having trouble putting all of this together, but here is the
scenario
ASP page with a Query String Variable,
Example:  http://mywebsite/mywebpage.aspx?variable=x

Dear experts
I have a customer requirement.  App is a C application deployed on Solaris.  
The database is inteded to be MS SQL SERVER 2000 or 2005.
Before I even get started, will Microsoft support such a mix - i.e.,

Is it possible to have an SQL Server NOT broadcast the fact it's an SQL
Server? In a school environment, with Visual Studio 2005, this product gives
the students a mite too much connectability to network resources. Would it
be possible to have a 'passive' SQL server? One that ...

I have installed Microsoft SQL Server Desktop on Windows Xp Pro. I can
connect to database from remote machines with Windows 98Se, but i can't
connect from machines with Windows XP.
                               Chris

We are running regression tests fro our product against MSS 2005 and the new
jdbc driver. However we are getting the following error message:
“com.microsoft.sqlserver.jdbc.SQLServerException: The conversion from int to
TIMESTAMP is unsupported”

I have installed SQL Server Express and uploaded an access database into it.
It's running properly. The problem is that I'm trying an VS-6 application to
connect to it using "SQL Native Client" I can connect if I use a "USER
defined DSN", but can not if I try to write connection ...

I've just built our new 2005 cluster and I'm having some issues with
connectivity via a client network alias.  It's a 2 node active/active 64 bit
Ent Edit, sp1, 32gb ram. Both nodes are listening on port 1433 with both tcp
and named pipes (although we never use named pipes)

I'm trying to refresh (re-read) the current row of an forward only cursor
but SQLFetchScroll and SQLSetPos will fail for this kind of Cursor. Is there
any way to do that?
Regards,

Pardon if this has been asked before.  If so, please post the URL.
Could someone please tell me how to fix this login/pipe?  Notice the 3rd
login is fine with "/E".  It is a SQL2005 Enterprise on Win2003 Server Ent.
C:\Program Files\Microsoft SQL