Garret, You've had exactly my problem. I've tried every type of combination. I must admit I thought you needed named pipes enabled but that may juet be a throwback from when I used SQLServer on NT - many years ago. The correct drivers are installed and TCP/IP is enabled.
The strange thing here is that I have the Northwind Example data installed and VS2K5 gan see the database fine but again, once I attach/create another .mdf database I can't see it at all. The connection manager in Visual Studio also refuses to see another database so it MUST be something to do with the way I have the database configured but I'm damned if I can find out what it is. This is driving me seriously mad. Dave Crozier The secret to staying young is to live honestly, eat slowly, and to lie about your age -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Garrett Fitzgerald Sent: 20 July 2006 01:49 To: [email protected] Subject: Re: Problems Connecting to M$SQLExpress On 7/19/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > From: "Garrett Fitzgerald" <[EMAIL PROTECTED]> > > > > I had a similar issue, where I could connect to SQL Server Express > > on my own machine, but the other folks in the office couldn't, > > despite allowing remote connections. Do you have to update to the > > latest version of the ODBC drivers on all machines that want to connect? > > Did you enable TCP/IP in the Configuration manager? Yup, TCP/IP and Shared Memory Enabled, VIA and Named Pipes Disabled. [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
