Kevin,

I think I finally caught a break on part of this. I had previously asked the hosting company about the dot net assemblies being installed on this server and both times got an affirmative reply. They went on to say they do not provide support for scripting or programming which I wasn't really asking for.

Today, I moved it up the chain to find out why the settings in my web.config were not being respected. Turns out they don't have dot net 2.0 installed on all servers. The server I am on while only indicating to me that asp.net is installed, only has dot net 1.x installed. They promise to upgrade this in 24-48 hours.

I presume once this is corrected I should be able to further test out the connection string.

Thanks of the help.
Tim

>>First the error message isn't very helpful as it suggests my web.config file has the following setting:
>>" customErrors mode = "Off" " and suggesting it should be:
>>" customErrors mode = "RemoteOnly" defaultRedirect = "MyCustomErrorPage.aspx" "
>>
>>My Web.config file does not have this set to off so why do I get this message?
>
>ASP.NET is giving you this error message, but I'm not sure why you're seeing it if it's set to "ON". Here's more information about this setting:
>
>http://riderdesign.com/articles/displayarticle.aspx?articleid=1
>
>>The real problem I think is the connection string for Access. The obvious problem is I have this in the "value=" section
>
>I'm wondering if this might be a permissions issue. Here's a link to an article on using an Access database from ASP.NET:
>
>http://www.aspfree.com/c/a/Microsoft-Access/Connecting-to-a-Microsoft-Access-database-with-ASPNET/
>
>Best Regards,