Accessing database in VB project

code_red · 07-15-2006, 07:21 PM

I was trying to make a database for my VB application (using VB express 2005). New Items -> SQL database. I never used the database before and I received this error. If the default settings is the problem, how do I change the settings to allow remote connections.

Here is the error in the screenshot.

Rakka · 07-15-2006, 07:41 PM

Silly question I know, but have you got your machine actually running a sql server? Or connecting to an existing SQL server?

code_red · 07-15-2006, 07:42 PM

I dont have a server or an IIS. I am just running the SQL server 2005 express edition as a database for my VB program (non web application).

Rakka · 07-15-2006, 07:50 PM

Quote:

Originally Posted by code_red

I dont have a server or an IIS. I am just running the SQL server 2005 express edition as a database for my VB program (non web application).

Sorry, I might be talking schite here....but, you're using VB 2005 express edition from teh screenshot. Never used it so you'll have to enlighten me... Does this automatically set up a local SQL server or is it something you have to set up seperately

code_red · 07-15-2006, 07:56 PM

It does not set it up automatically. The error says that I have to set it up myself.

It tells me to switch the settings so I can access the sql server on my server which I dont have and I dont need for my vb application.

SQL server express 2005 is the only database application that supports VB express 2005.

Rakka · 07-15-2006, 08:08 PM

Quote:

Originally Posted by code_red

SQL server express 2005 is the only database application that supports VB express 2005.

sorry to spam...because I'll have to take your word for it...but....MS don't support VB xpress 2005 with access databases anymore? That's a good thing btw. mdb driven things are ...well... lame with all the db merging and all

but...I'm lost. Getting down to basics, Are you asking for help setting up an SQL local server?

code_red · 07-15-2006, 08:10 PM

Quote:

Originally Posted by Rakka

sorry to spam...because I'll have to take your word for it...but....MS don't support VB xpress 2005 with access databases anymore? That's a good thing btw. mdb driven things are ...well... lame with all the db merging and all

but...I'm lost. Getting down to basics, Are you asking for help setting up an SQL local server?

I think it might be part of the solution. Yes.

Rakka · 07-15-2006, 08:15 PM

Then hopefully some techie type ike Mikey (Stuble U) might read this. Then I can listen and learn since I could do with tutoring with this sort of thing.

I did once find some easy setup utility but I'm damned if I can find it again now =/

..:: shouts @ Mikey ::..

DR Evil · 07-15-2006, 08:55 PM

would this website help you?
http://www.aquesthosting.com/HowTo/S...QLError26.aspx

I have used both dbs and vb but never done what you are trying to do. when ever i get errors though i write the error number down and google it

i did this and found this

Quote:

Cause & Fix #1:

Cause: Server not configured for remote connections.
The error is telling us that your server has not been configured to allow remote connections. If your SQL Server has not been configured to allow remote connections, then configure your SQL Server.
Fix:
SQL Server 2000: Open the SQL Server Client Network Utility. On the General tab enable the protocols you need to use. Typically this will be 'TCP/IP' and possibly 'Named Pipes'.
SQL Server 2005 Open SQL Server Configuration Manager. Select "SQL Server 2005 Network Configuration | Protocols for MSSQLSERVER" then enable the protocols you need.

Cause & Fix #2:

Cause: ASP.Net 2.0 Providers are trying to pull from the server's (nonexistent) Providers database.
By default the machine.config file is trying to pull the Provider information from a SQLExpress database using an invalid connection string named "LocalSQLServer". Many web servers will not have SQLExpress enabled, and will not have this value set to a valid SQL Server database that is of use to you. In a shared hosting environment, this is especially true, as it would be expected that you would want your Provider information stored in your database and not some single database shared by the other users of that web server.
Fix:
Since you probably cannot access the machine.config file, you need to override the Provider settings in your web.config file, and set the connection string name to your connection string name. The following code comes from the machine.config file and has been modified to first remove each provider before adding the provider.
Add the following code to your web.config file just under the "<system.web>" tag.
Make sure to replace the 3 occurrences of connectionStringName="LocalSQLServer" with your connection string name.

I Only have the old free VB so I dont know myself... Good job though because i suffer from computer rage

code_red · 07-15-2006, 10:03 PM

Did not work. Maybe I can install an IIS so the SQL program can reconize it as a server.