ASP.NET OLE DB Connection not working

IMHO if you are serious about doing work in the .Net2.0 framework then you
should forget DW for anything other than designing the pages. It can't
render most of the controls, and its Data access is extremely limited.

--
Paul Whitham
Certified Dreamweaver MX2004 Professional
Adobe Community Expert - Dreamweaver

Valleybiz Internet Design
www.valleybiz.net

"InPlayTech" <webforumsuser@macromedia.com> wrote in message
news:es9rdp$8ll$1@forums.macromedia.com...
> OK, I found a sort of work around, so hopefully this helps. First off,
> I'm
> running winXP SP2 and the .NET 2.0 environment. Not sure if that plays a
> roll,
> but I thought I'd throw that out there anyway.
>
> Here's a recap of my problem: I want to use the Application panel in DW8
> to
> manage my DB connections. The connection string provided by GoDaddy did
> not
> work there. Meaning, it would say that it connected successfully to the
> sql
> server, but when I opened the DB it did not show any tables. If I
> uploaded the
> code anyway and hand coded a dataset, it worked.
>
> In playing with my connection string, I realized that the problem lies
> with
> this:
>
> Provider=SQLOLEDB;
>
> If I remove the provider info, then DW8 has no problem viewing tables in
> my
> SQL DB. However, the webserver could not connect to the DB with out it.
> So
> what I decided to do is have two copies of the web.config file. The
> version on
> the server will include the provider line. On my local machine it will
> not.
>
> I'm sure there are better ways to accomplish this, but this is the only
> working solution I could find. Honestly it seems like a DW issue to me,
> so
> that's where I put the blame, but I really don't care now.
>

check your private messages

I changed to conn string to match what you suggested, now DW no longer sees any tables in the Application Pannel.

Here's the stuff from my web.config file:

<appSettings>
<add key="MM_CONNECTION_HANDLER_CUSTOM_CONNECTION" value="sqlserver.htm" />
<add key="MM_CONNECTION_STRING_CUSTOM_CONNECTION" value="Persist Security Info=False;Data Source=10.0.9.17;Initial Catalog=*********;User ID=********;Password=******;" />
<add key="MM_CONNECTION_DATABASETYPE_CUSTOM_CONNECTION" value="SQLServer" />
<add key="MM_CONNECTION_SCHEMA_CUSTOM_CONNECTION" value="" />
<add key="MM_CONNECTION_CATALOG_CUSTOM_CONNECTION" value="" />
</appSettings>

Basically just create a new SQL Server connection from the application panel under databases. Then type in the IP in serverName field.

Okay lets try this, modify your web.config at this key:

<add key="MM_CONNECTION_STRING_yourConName" value="Persist Security Info=False;Data Source=[serverIP];Initial Catalog=[databaseName];User ID=[username];Password=[password];" />

I don't know why you are having so much trouble connecting to this database. So you entire thing will be similar to:

<add key="MM_CONNECTION_HANDLER_test" value="sqlserver.htm" />
<add key="MM_CONNECTION_STRING_test" value="Persist Security Info=False;Data Source=[serverIP];Initial Catalog=[databaseName];User ID=[username];Password=[password];" />
<add key="MM_CONNECTION_DATABASETYPE_test" value="SQLServer" />
<add key="MM_CONNECTION_SCHEMA_test" value="" />
<add key="MM_CONNECTION_CATALOG_test" value="" />

I think its related to this:

http://www.adobe.com/go/455d4ca0

Unfortunately, I've done the fix, and it still doesn't work.

The DB connection still seems to work in DW, but if I open a test page I get the following error:

System.ArgumentException: Keyword not supported: 'driver'.
at System.Data.Common.DBConnectionString.ParseInternal(Char[] connectionString, UdlSupport checkForUdl, NameValuePair& keychain)
at System.Data.Common.DBConnectionString..ctor(String connectionString, UdlSupport checkForUdl)
at System.Data.SqlClient.SqlConnectionString..ctor(String connectionString)
at System.Data.SqlClient.SqlConnectionString.ParseString(String connectionString)
at System.Data.SqlClient.SqlConnection.set_ConnectionString(String value)
at System.Data.SqlClient.SqlConnection..ctor(String connectionString)
at DreamweaverCtrls.DataSet.NewDbConnection(String strConnection)
at DreamweaverCtrls.DataSet.DoInit()

Any other thoughts?

On the custom connection string in the web.config did you change:

<add key="MM_CONNECTION_DATABASETYPE_test2" value="OleDb" />

to

<add key="MM_CONNECTION_DATABASETYPE_test2" value="SQLServer" />

Well it has to be something with the conneciotn string. If you were able to see the tables with the custom string, but not the other, I am guessing it has something to do with the Data Source. Try placing the IP address there instead of the name of the server. You could also send me a private message with the connection info, so I can try it on my machine to see if will work or not.