Eduardo Lorenzo

Ok, here it is.

I put this:

in the Web.Config. But when I try to use Server.MapPath, it gives back an error! Server --- not defined.

What gives?

Eduardo Lorenzo

also.. I am calling the appsetting in my DAL, in the class, and Server.MapPath also does not function there.

reboot

Is this a webforms application? If it is, then you don't need Server.MapPath to find the web.config. If it isn't, then duh.

Eduardo Lorenzo

yes this is a webform, that's why I have a web.config

I'm not using server.mappath to find web.config, I'm trying to change the connection string. The static connection string "C:/.../mytable.mdb" won't work because the table is now located in the webhost and I can't seem to use the url "www.sitename.com/tables/mytable.mdb" as part of the connection string.

shaul_ahuva

Most hosting providers will give you either the physical path of your site or an ODBC DSN to use. Do you have anything from them regarding the physical location of your files?

Eduardo Lorenzo

just the URL.

I have resolved this issue (a bit) by placing the Server.MapPath call within the pages and the Driver, password, and other connection string information in Web.Config.

shaul_ahuva

That was going to be my next suggestion with the caveat that you should check to ensure you site is not being hosted in a web farm/garden (which would obviously cause serious problems with any file references).

wayneph

The whole point of a .config file is that it probably changes from machine to machine. I have a hardcoded path in my web.config on my test machine. I have a different hardcoded path in my web.config on my production machine. When I move files to production, I just don't change the config.

Using .NET 2.0, Microsoft has a Tool (Web Deployment Projects) that makes the process a little easier. See Scott Guthrie's blog here: http://weblogs.asp.net/scottgu/archi...06/429723.aspx