SOLVED SOLVED SOLVED I really hate Microsoft when they do this. If I were to ask which "Server" you were using to find the database I guess you would all simply specify the machine name - especially if that was the default value prompted for within the connection manager.
However Microsoft in their infinite wisdom don't really want the server name they want the instance name i.e <server>\sqlexpress as opposed to <server>. I must admit that one is REALLY bad when it comes to interface testing and documentation on M£'s behalf. I wonder how many people have simply given up like Vassilis. Still, at least I don't have to reinstall VS2K5 again. Thanks to everyone for all the helpful tips - and just put this one on the "DON'T FORGET" list when using SQLServerExpress. 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 Vassilis Aggelakos Sent: 19 July 2006 16:53 To: [email protected] Subject: Re: Problems Connecting to M$SQLExpress I had the same problem with VFP 9 and Sql Server 2005. I did a typical installation of Visual Studio 2K5. I never managed to connect within VFP in my local machine. I gave up and I forgot it... --Vassilis Aggelakos ----- Original Message ----- From: "Dave Crozier" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, July 19, 2006 6:28 PM Subject: RE: Problems Connecting to M$SQLExpress > Stephen, > I installed it automatically with Visual Studio 2K5. I can see the server > within 2K5 no problems but not from VFP and to set up a data source. I > might > just uninstall the whole lot and start again but it's a 3-4 hour job! > > > 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 [EMAIL PROTECTED] > Sent: 19 July 2006 16:18 > To: ProFox Email List > Subject: RE: Problems Connecting to M$SQLExpress > >> On 7/19/06, Dave Crozier <[EMAIL PROTECTED]> wrote: >> > >> > If I try and create a connection within the VFP DBC I get two >> > possible choices "SQL Server" and "SQL Native Client", both of which >> > don't seem to work either so I guess there is little hope with a >> > DSNless > attempt! > > You need to use SQL Native Client, that is the 2005 version. > > I just made one and can use it in Excel. > > Who installed the SQL? Did you open it up for use? Did you allow TCP/IP? > You see the new version comes locked down and you have to actually open up > what and how to connect to it. > > Secondly, how are you connecting? Goes back to last Q, in that how was > the > server configured? > > Just because it's not easy doesn't mean it's not working. It may be > working > according to the current install plan. No users or connections until > someone defines what they will be. > > HTH. > > > [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.
