Database connectivity from ASP.NET pages hosted on a free web server?

[JKidd32]

Hi I am new to these forums and was hoping that somebody could help me out with a problem I have come across.

I have built an ASP.NET website with C# coding which queeries an Access database. I have tested it thoroughly on the web matrix test server and the functionality is all working. I now want to upload the pages to an online webserver so that they can be accessed from any computer.

I am trying to find out whether the only changes I need to make are in the connection string in the web.config file; or if I need to do something else.

Here is my web.config file:

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<appSettings>
<add key="ConnectionString"
value="Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\\Assignment\\magazine.mdb" />
</appSettings>
</configuration>

If it is just a case of changing the ConnectionString then please could someone advise me on the changes I have to make. Any suggestions are welcome.

I have looked at a lot of Googled ASP.NET help sites and have found myself going round in circles for hours and not getting a solution.

Many thanks
Jon

[benbramz]

i dont really understand the question - but from what i gather, your your moving your pages and database to a server somwhere, not your local machine?

in that case would you need to change the connection string to server.mappath ....
for example, :

Code: Select all

data source=" & server.mappath("db.mdb"))

[Smokie]

You need to know the full path to your database when it is on your live website, the easiest way to do this is to create a simple .asp page, insert the following code, and upload it:

Code: Select all

<%=Request.ServerVariables("PATH_TRANSLATED")%>

when you view this page it will give you something like:

e:\sites\domain.com\web\

This is the path you'll need to use in your Web.Config file, for example:

<add key="ConnectionString"
value="Provider=Microsoft.Jet.OLEDB.4.0;Data Source=e:\sites\domain.com\web\magazine.mdb" />

[JKidd32]

Thanks BenBramz and Smokie for the replies.
I have sorted the problem now. Many thanks to Smokie who I wrongly read his advice and made a simple .aspx page instead of a simple .asp page.
It is sorted now: many thanks.
Jon