Database Connection ASP.NET Issue

[trocat]

Using DW MX 2004 on windows XP SP2, IIS, using ASP.NET, VB for code, Access
2000 DB, I create a OLE DB database connection using the connection template
(since the 'Build' app won't load), I test the connection and the test is
successful. However, there are no tables shown. I have read the 'fix ' tech
note [url]http://www.macromedia.com/cfusion/knowledgebase/index.cfm?id=tn_19515[/url].
Downloaded the extention and followed all the examples here in the DW forum but
still have not luck making a successful connection. I'd sure like to be working
on the site rather then mess around with this part of the the process (DW sure
makes a day productive. Not!). Anyone know of a sure fix for this issue? Any
help from those of you in the 'know' would be splendid! Thanks for reading.
TroCat

[TrevorTaylor]

In my opinion, Macromedia have done a very poor job of handling this problem.
It has been a known problem since at least October last year, and their "fix"
is a pain in the neck to use.

Firstly, make sure that you can view a plain ASP page (not ASP.NET) on your
localhost. This is necessary because the connection scripts use ASP. (Not
ASP.NET -- go figure!) If your IIS server is not working properly, then you
will be wasting your time trying to get a database connection working.

Next, for EVERY site that you currently have defined, you need to go to Sites
\ Advanced \ Remove Connection Scripts. Then you have to delete your database
connections. Open the database connection first and copy the Connection String
so that you don't have to type it back in! After deleting a connection,
re-create it using the connection string that you copied and click on the Test
button in the DB Connection window.

This procedure copies the new connection scripts into the _mmServerScripts
directory which is located in your web site. I have experimented with just
copying the scripts in there manually and it seems to work, but I don't know
what other things might be happening behind the scenes, so I can't recommend
this.

If you want a quick check, look in the _mmServerScripts directory at the size
of MMHTTPDB.js -- the new one is 27KB, and the old one is only 25KB.

The problem with the Build button is still not fixed and I personally believe
that the explanation of how to use a UDL file on the support web site is not
very good. Most people don't realise that a UDL file is just a text file and
you can open it in Notepad to copy the Connection String.

Let's hear from Macromedia. Are you guys out there? Do you actually monitor
your own forums?

Trevor

[trocat]

Thanks for the input Trevor. I'll see if I can get it work with your advice.
RE: Macromedia, yeah I think they are are poor at fixing bugs with their
software. My speculation on that is: they realize the problem, ignore the
current version issue and move right on to the next release, with a fix of
course. Then proceed to push users to buy the new release instead of fixing the
current version! IMHO I think we should get some kind of $ refund when the
program does not work as it claims. You know, less features, less money!
TroCat