Hi Nicholas!
At the configuration option, both named pipes and tcpip is selected. The
following is the error message:
You have connected to a version of SQL Server later than SQL Server 2000.
The version of Visual Studio or Access that you are using was released before
the version of SQL Server to which you are connected. For this reason, you
might encounter problems.
Please check with Microsoft to see if there is a service pack that you
should apply to Visual Studio or Office in order to get support for the
version of SQL Server to which you are connected.
You can continue but any new object types might not be enumerated, and it
will not be possible to save any objects or database diagrams that you create
using the Visual Database Tools.
"Nicholas Paldino [.NET/C# MVP]" wrote:
Belee,
I think that by default, SQL Express only uses shared memory for
communications. I think that you have to go and enable the named pipes
option for the server in order for VS.NET 2003 to work.
Hope this helps.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com
"Belee" <Be***@discussions.microsoft.com> wrote in message
news:4F**********************************@microsof t.com... 1. I am using sql server express and visual studio 2003. I have been
able
to create the connection to the database in server explorer but cannot
update
table definitions. It gives an error that I may need a patch or changes
would not be saved. So I have to do the table changes in SQL Express
Management studio.
2. When I modify a stored procedure in the management studio of sql
express, it does not update but rather saves it the changes in a querry
file.
But when I do it from visual studio 2003 server explorer and refreshes it
works.
3. I want to also use sql native client for my odbc configuration, no
problems?
The bottomline, I need help!!!!!!!
