I don't understand what is happening with DWMX. I can't find a pattern to what's happening but it's driving me nuts.
I have a web (or hope to have) that enables pilots and flight crew to post resume info in the hopes of snagging a job with an executive jet operator.

I have 6 different Enter Data forms, most of the simpler ones work fine. The "Enter Resume" is a particular proble, It contains 55 fields that are a mixture of 15 dynamic lookup fields, dates fields, check boxes and even had ASPpload 2.09. ASP Upload has since been removed but did't fix the basic issues.

I had it working fine using a DSN connection. Client wanted some changes, form field text, add a field here, remove one there.
The usual stuff...The whole "Enter Resume" form page went to @#%$ in a handbasket.

What happens after opening a page that was ok 5 minutes ago:
- Server Behaviors that were good show the red exclamation... they can't find the datafile refered to in the connection asp file. But double clicking and selecting the same connection from the drop down (that's always been there but isn't selected now) makes the connection valid once again and the exclamation disappears.

- DWMX doubles or triples the reference to the connection file <!--#include file="Connections/fodData.asp" --> is in the source 2 or three times

- Changes field names and then reports a "duplicate output error" trying to load the page. Fields MedicalFC and MedicalExpires both become MedicalFC!

- Live Data View used to work, now it locks up the PC unless I remove ASP Upload, which I didn't have to do before.

- Double clicking on a Recordset that is linked to a Sever Behavior that is no good anymore gives the correct Recordset Name, correct Connection (sometimes) and the correct tablename but the column names shown are not the ones from the table it's referring to!!

I'm going nuts here. DWMX is becoming extremely twitchy to put it nicely. One step forward and two back. I's almost like something about the form is confusing DW and causing these issues.

I've removed and reinstalled DWMX and the 6.01 Updater three times. No change I'm using IIS5 (from WinXP Pro)updated to MDAC 2.7 Refresh.
Because it was losing the connection to the datafile and the behaviors I tried a DSN-Less connection (below) to my local server.
<%
' FileName="Connection_ado_conn_string.htm"
' Type="ADO"
' DesigntimeType="ADO"
' HTTP="false"
' Catalog=""
' Schema=""
Dim MM_fodData_STRING
MM_fodData_STRING = "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=D:\Inetpub\wwwroot\fodsDevNew\fpdb\foddata.mdb;Persist Security Info=False"
%>

No change, all of the above continued to happen.

WindowsXP is stable for all other apps. Photoshop, ImageReady, CorelDraw, Ghost Recon etc. They're running on a ASUS mobo, Pentium4 3.06 GHz, 512Meg RIMM4200...plenty of resources.
I'm at the point of re-installing Windows XP and if no luck, giving up on DWMX

Can anyone see a pattern here? Is there a certain order of doing things in DWMX that I don't know about?

You are not alone, I have had similar problems, although not as severe, with DW losing recordsets, usually cured if I close the page and re-open it the recordset re-appears, but I have 2 #Include connection lines. In some cases I have to close and re-start DW altogether.

DW's latest quirk is to complain that my system doesn't have enough memory, this started happening after I installed a further 512Mb of RAM to bring the system total up to 1024Mb, If I clear the message DW runs fine-ish.

I also have an ASUS motheroard, but with an Athlon processor and Windows 2000 pro, like you, all other applications run flawlessly.

I like DW, and on the whole think it's a great product, but think there is definately room improvement in the testing, de-bugging and quality controll department.

Regards

Owen.

-------------------------------------------------------------------------------------------
Used programming books and web development software for sale (UK only): www.tdsf.co.uk/tdsfdemo/Shop.htm

Developer services and tutorials: www.drdev.net

Multiple Parameter UD4 / Access 2000 Search Tutorial: www.tdsf.co.uk/tdsfdemo/

I am in the same boat, I retired DWMX for all but ColdFusion MX development. I am using Ultradev for everything else, there are too many things that can go wrong.

Macromedia never got back to me about the status of the 500 page template bug and it is not listed on any bug list (if you can find one, that is), so I am sticking with UltraDev for our 1500 page ASP application.

With regards,

Dennis van Galen
Webmaster KPN Telecom Holland
Financial & Information Services

I'm sorry to hear that others are having these issues as well.

I have looked thru this forum and others and have seen similar issues. I have also read about users who sound like pros who have NOT had any issues. How do they do it? I would really like some tips from these users describing how they avoid problems with DWMX.

My plan now is to remove and recreate all the recordsets and server behaviors and recreate the page. Since I don't have the same severity of problems with other pages (smaller forms, search and display pages etc, an entire security and admin system) I think I'll try recreating the more complex forms and see what happens.

I've just spent the day recreating the forms that were the biggest offenders.
Removed ASP Upload 2.09!! from the system and did not re-install
Deleted the recordsets, the behaviors and recreated all.
Client had more changes today and all went well with no glitches!!!

Could it be ASP Upload? I serously doubt it. Could the accumulated changes somehow confused and corrupted the code? I choose the latter.

Anyway I'll stick with DWMX for a while longer and then if all else fails I'll take the suggeation to go back to UltraDev. Wonder where I put that......

Thanks for the support and advice