First: the add key="" that was how I setup my config files in .NET 1.1 I have not yet used 2.0 but if they are using add name="" then use that.

In so far as your error: You checked permissions but did you check to see if the directory IS an application?

================================================== =========
I will only tell you how to do it, not do it for you.
Unless, of course, you want to hire me to do work for you.
================================================== =========
http://www.catb.org/~esr/faqs/smart-questions.html
^^Took that from planoie's profile
================================================== =========

Hmm.. how can I check that on the godaddy's server? I created directory in the hosting manager and read/write/web enabled it. There is a "set root": box but I didn't chk it--as I think it would make it the site root.

What comes up must come down. [The single-most underrated quote of all time]

here are the app settings:

    <appSettings>

      <add name="ConnectionString" value="Provider=SQLOLEDB;Password=xxxxxx;Persist Security Info=True;User ID=xxxxxxx;Initial Catalog=xx_xxxxxx;Data Source=xxxxx-v02.xxxx.xxxx.secureserver.net" />
      <add name="SmtpServer" value="mail.xxxxx.biz" />
      <add name="MailFrom" value="[email protected]" />
      <add name="SiteAdminEmail" value="[email protected]" />
      <add name="SiteAdminPhoneNumber" value="(123)123-1234" />

      <!-- add name="pubsConnectionString1"
            connectionString="Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirector y|\pubs.mdf;Integrated Security=True;User Instance=True"
            providerName="System.Data.SqlClient" /> -->

    </appSettings>

What comes up must come down. [The single-most underrated quote of all time]

I know nothing about godaddy I know in IIS i right click on the folder, select properties, and define that folder as an application. You might want to call their Techs and ask them to ensure that the directory is running as an application as I have only ever seen this error when a directory was not setup as an application.

================================================== =========
I will only tell you how to do it, not do it for you.
Unless, of course, you want to hire me to do work for you.
================================================== =========
http://www.catb.org/~esr/faqs/smart-questions.html
^^Took that from planoie's profile
================================================== =========

Thanks. On hold with them now.

You don't think it would have something to do with the fact that the default connection explicitly calls the mdf (AttachDbFilename=|DataDirectory|\pubs.mdf) but I haven't done so in my new connection string?

What comes up must come down. [The single-most underrated quote of all time]

No because that key isnt actually being used until you make a call to the database. If that were the problem though, you would you would probably get a permissions error or something to that effect.

================================================== =========
I will only tell you how to do it, not do it for you.
Unless, of course, you want to hire me to do work for you.
================================================== =========
http://www.catb.org/~esr/faqs/smart-questions.html
^^Took that from planoie's profile
================================================== =========

OK, solved the connection issue (had to ENABLE ROOT in godaddys hosting manager). Now I have a new error:

 Configuration Error
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: Unrecognized configuration section system.web/appSettings.

Source Error:

Line 97: />
Line 98:
Line 99: <appSettings>
Line 100:
Line 101: <add name="ConnectionString" value="Provider=SQLOLEDB;Password=xxxxx;Persist Security Info=True;User ID=xxxxx;Initial Catalog=DB_xxxxx;Data Source=whsql-xxxx.xxxxx.secureserver.net" />


Source File: d:\hosting\zzzzzz\application\web.config Line: 99


What comes up must come down. [The single-most underrated quote of all time]

Ok I have to ask this: the site you are deploying, are you deploying it under the .1.1 framework or the 2.0 framework?

In 1.1 your config might look like this

<configuration>
<appSettings>
<add key="name" value="" />
</appSettings>
</configuration>

In 2.0 it might look like this:

<configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0">



  <appSettings>

    <add key="name" value="value" />

  </appSettings>



  <connectionStrings>

    <add name="dev" connectionString="..."/>

    <add name="live" connectionString="..."/>

  </connectionStrings>



================================================== =========
I will only tell you how to do it, not do it for you.
Unless, of course, you want to hire me to do work for you.
================================================== =========
http://www.catb.org/~esr/faqs/smart-questions.html
^^Took that from planoie's profile
================================================== =========

Using 2.0 and have in it what you mentioned

The problem now seems to be with the fact that some of the scripts call the default connection string .. but as I stated earlier, since the string does not contain the reference to the MDF, the call is made to the SQL Server and of course SQL server will not find the tables the script is asking for because all of the tables are in the MDF. So how do I make it so the string uses SQL Server as the provider, but the MDF as the source?

Here is the original string (A) and the modified string I am using now (B)


A)

<connectionStrings>
  <add name="pubsConnectionString1"
    connectionString="Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirector y|\pubs.mdf;Integrated Security=True;User Instance=True"
    providerName="System.Data.SqlClient" />
</connectionStrings>


B)

<connectionStrings>

<add name="pubsConnectionString2" connectionString="
Server=whsql-v04.xxxxx.xxx.xxx.net;
Database=DB_xxxxx;
User ID=xxxxx;
Password=xxxxxx;
Trusted_Connection=False" providerName="System.Data.SqlClient" />

</connectionStrings>

What comes up must come down. [The single-most underrated quote of all time]

Ohhhhhhhhhh. You need to import your SQLExpress database into the SQL Server. Unfortunately I, again, can't help you because you dont have physical access to the SQL Server. Although, to save you a call into tech support check 2 things:

1)See if there is a way to import your source MDF into their SQL Server through their web interface. I know it can be done through Enterprise Manager.

2)See if you can import SQL Scripts and have the script generate the tables and such for you, if you can, have SQLEXPRESS Script your database and import that.

================================================== =========
I will only tell you how to do it, not do it for you.
Unless, of course, you want to hire me to do work for you.
================================================== =========
http://www.catb.org/~esr/faqs/smart-questions.html
^^Took that from planoie's profile
================================================== =========