Database Connection Problem

[greenhart]

Using ASP.NET C#, I can connect to a database by adding a new connection (OLEDB), and the connection tests OK, but no tables are shown.

If I use ASP VBScript, the connection, using a connection string, works fine and the tables are shown.

I have tried both Access and SQL Server 2000 databases, with the same result.

Thanks for any advice.

[greenhart]

P.S. Windows XP SP2, Dreamweaver MX 2004, .NET 1.1 and 2.0

[Newsgroup_User]

Hi yea,
compare your connection string to one of these

http://www.connectionstrings.com/?carrier=sqlserver


k




"greenhart" <webforumsuser@macromedia.com> wrote in message
news:f4an2n$j7d$1@forums.macromedia.com...
> P.S. Windows XP SP2, Dreamweaver MX 2004, .NET 1.1 and 2.0

[greenhart]

I've tried several connection strings - to Access, and SQL Server, They all test OK, but the tables in the databases are not shown in the Databases panel.

[Guest]

Check out this document. I am having the same problem:

http://kb.adobe.com/selfservice/viewContent.do?externalId=455d4ca0&sliceId=1

[greenhart]

Thanks for the suggestion. Unfortunately, I have tried the measures detailed for XP2, and have gone from bad to worse. Now the connection will nto even test - I get the error: HTTP Error Code 405 Method Not Allowed

So unless somone comes up with further info I am giving up and will code the connection strings myself, using something like:

connectionString = "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" + Request.ServerVariables("APPL_PHYSICAL_PATH") + "Assets/Database/trio.mdb";

Cheers,

[greenhart]

Well, after realising how much code Dreamweaver automatically generates for a DataSet, and realising that I would have to write it all from scratch (yawn) I did a bit more digging.

The first thing I did was disable the newly installed Dreamweaver Extension - see the link below, under the heading "Database connectivity fails with local ASP.NET and ASP servers"
Dreamweaver and Windows XP SP2

And hey presto! suddnely the tables magically appeared, and I could set up a dataset and bind it to a table.

But then I found that I needed Dreamweaverctrls.dll. The following line did not parse:
<%@ Register TagPrefix="MM" Namespace="DreamweaverCtrls" Assembly="DreamweaverCtrls,version=1.0.0.0,publicKeyToken=836f606ede05d46a,culture=neutral" %>
(also see this link:
File or assembly name DreamweaverCtrls was not found

I tried Deploying as suggested, which put Dreamweaverctrls.dll in the site's root folder. Unfortunately this does not work, and you still get the parsing error. First you have to create a bin folder off the site root, and then deploy, and the dll is put in this folder.

And now everything works!!!
Well.. there is still some problem with the Build function, and udl files, but I can live with that.

[greenhart]

Well, so much for my hopes ... I am once again back to square one. I have Connections that test OK, Datasets that return records, but the connections in the Database window show "No Tables"

Somehow I managed to get them back by deleting every Dreamweaver -generated file, but now they have gone again for no apparent reason.

And still the so-called "XP SP2 DB connectivity Fix" cannot be enabled, or I get nothing but the "Error 405 Method Not Allowed."

Is there anyone at all who has surmounted this problem? Doens't anyone use Databases with Dreamweaver?

[greenhart · Accepted solution]

Well, after some investigation I found a workaround. The Dreamweaver extension for XP SP2 causes the HTTP Error 405 Method Not Allowed. I cannot find any way around that (see this link for information though it didn't really help me:
http://support.microsoft.com/kb/216493 )

It seems that something Dreamweaver is POSTING (or other) with a \ appended to the URL, and causing the error. I have no idea how to fix that.

However, I found that the if I installed the XP SP2 Extension, then saved the updated ASP.NET and ASP script files
(in D:\Program Files\Macromedia\Dreamweaver MX 2004\Configuration\Connections\Scripts), the removed the XP SP2 Extension, then overwrote the pre-extension scripts with the updated ones I had saved, I can now browse tables, etc in the Databases window.

So the problem is not really fixed but I can finnally get on with life!!!