Dynamic Site Requirements Go Dead

[rexburg]

When a site is defined to use ASP VBScript and a new dynamic page is created,
the Application panel allows a new Database connection to be created. Following
the creation of the connection, recordsets can be created and used. However, as
soon as the dynamic page is saved all objects in the Application panel are
greyed out and no longer work. Has anyone seen this before and know a
workaround. I am using Dreamweaver MX (not 2004) on Windows XP Pro. Editing
local, posting remote to an IIS 6 server via FTP. The dynamic page is being
saved within the defined site and the remote and testing server are one in the
same. Any response will be greatly appreciated.

[sasquatch72]

Had a similar problem; stepped back, took a breath and realised that in haste I
was creating new ASP pages as ASP JavaScript (default choice when creating a
new dynamic page) instead of VBScript as I had set up the application server.
Seems silly now, but take a look at the first line of code on all of your ASP
pages and see if the is a mix of Script language being specified. If not, then
forget I mentioned it.