"Birk Binnard" <birkb@NOSPAMbirkbinnard.com> wrote in message
news:%23rYi1qDOHHA.992@TK2MSFTNGP06.phx.gbl...
>I installed the latest version of VB Express & SQL Express with no trouble.
>VB fails to connect to any database -- even the sample applications fail
>with an SQL Exception:
>
> System.Data.SqlClient.SqlException was unhandled
> Class=20
> ErrorCode=-2146232060
> LineNumber=0
> 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 under the default settings SQL Server does not allow remote
> connections. (provider: Named Pipes Provider, error: 40 - Could not open a
> connection to SQL Server)"
> Number=2
> Server=""
> Source=".Net SqlClient Data Provider"
> State=0
>
> Since everything is on my local PC why would there be a reference to
> remote connections?
>
> I'm sure this is something simple -- but what?
>
> Thanks
>
> Birk Binnard

"Birk Binnard" <birkb@NOSPAMbirkbinnard.com> wrote in message
news:e88YJJMOHHA.4376@TK2MSFTNGP02.phx.gbl...
> Thanks, but after several hours of reading and experimentation I am still
> unable to get VBExpress to run any application that uses any SQL database.
> Even the DVD Collection template fails to run properly -- it starts and
> ends with no screen output at all.
>
> My original objective was to convert an old Access application to a
> stand-alone EXE that would be easily portable (and saleable) to clients
> with no software installed other than regular Office. I initially tried
> to get VBExpress to connect to my Access MDB file, but was unable to do
> this (the dialog box that builds the connect string doesn't work.) So I
> thought I'd try SQLExpress figuring VB needed something that was .Net
> compliant.
>
> After this experience its clear I'd be much better off converting the
> Access tables to plain old VB data files. That way my app will be
> independent of other software and I'll be able to ensure it will install
> and work OK the first time.
>
> It does seem odd that MS would allow "sample" software to be distributed
> that in fact does not work immediately following installation. The fact
> that there are KB articles explaining how to make things work is shocking.
> I know that if I tried to put software like this in a client's environment
> I'd be out of business in no time.
> --
> Birk Binnard
> http://www.birkbinnard.com