I have encountered many bugs in DMX and DMX 2004 which drove me coconuts.
I don't mean an occasional crash, but DMX messing up my (ASP) code. And even to such an extends that DMX became practical unworkable. Further i noticed that many commands returned errors because of missing javascript files. After investigating i noticed that some fysical paths in DMX's configuration folder were incorrect.

Searching the web learned that large array's of collegues have the same mad making experience. But i also learned that many of them have no problems.
In my case and in their cases the errors seem somewhat random.
I reinstalled a few times and after 4 days (count the financial damage!) i finally think that i might have gotten an answer.

My situation:
XP Pro on a fast machine with lots of RAM.
I have been using Dreamweaver since version 3 and my all time favorite was Ultradev.
Then upgraded to DMX 6, which i installed next to Ultradev.
Then i swapped DMX6 for DMX 2004.
And i installed the updater to 7.01.
I am hooked on all those handy extensions and i have quite a collection of them.

My problems started suddenly to appear overnight. Suddenly? Of course not. In computerland there is no such thing. Nothing "just happens". There is a cause for everything.
I suspected an extension to be to blame.

So i uninstalled all extensions. No result.
I reinstalled DMX. No result. Did it again. And did it again. (everytime in a slightly different way). Nothing worked. DMX kept messing up my code.

But a guy can't spend days debugging Dreamweaver. There is money to be made and children have to eat. So i wanted to get some real work done in Ultradev. To my horror Ultradev crashed on start up. Was there a connection between the problems? Then i noticed that DMX had a few configuration folders it shared with Ultradev. Huh? Yes, i know it shouldn't happen and one can blame MM for sloppy programming. But it was a fact. I also saw i had more then one configuration folders. One was in "documents & settings > all users > application data > etc", the other one in my personal user-account of XP.
It was obviously a mess.

So this afternoon i de-installed Ultradev AND DMX. Then i used a registry cleaner to get rid of all stuff in my registry that looked like the word NightmareWeaver of Ultradev.
Then i did that again, manually, searching the registry, and deleting everything DMX/Ultradev related.
I threw away all config-folders.
In a.w. i cleaned up the entire mess.

Reinstalled DMX 2004.
Surprise, it now runs fast en flawless.
For the last hour that is.

I have no idea whether the problems were created by installing DMX while old configuration-files from other Dreamweaver-versions where still on my machine, or that it was caused by a extension. Or both.

I have installed a utility now to backup and restore the DMX configuration and sites.
So i can now - carefully - start to install the update to 7.01. If that works out i will backup my configuration.
Then i will install my first extension.
If that works out i will backup my configuration.
Etc, etc.

Ver annoying and uncertain feeling, but i hope this will work.

Keep you posted!

Greetings from Holland

Download for free Dreamweaver backup-utility:
mm-exporter.joexx.de






The client is allways right even if he is not.

Edited by - tjerk on 10 May 2004 19:28:06

Edited by - tjerk on 10 May 2004 19:28:36

Aiaiai! Things are totally wrong again!

Tried to insert a record (ASP) using the standard insert-SB.

Before that, this was my form-tag:
<form action="" method="get" name="formbestel">

After applying the Insert record-SB:
<form actio<%=MM_editAction%>n="" methoPOSTget" namformbesteltel">

I just installed the updater-fix from MM.
S-h-i-t!!!!


Is there somebody out there who knows a solution?

Edited by - tjerk on 10 May 2004 20:03:41

Edited by - tjerk on 10 May 2004 20:04:24

after all your hard work cleaning your registry, im surprised you put the updater in due to the bad press it's been getting.

if i were you, i'd do it all again, and leave well alone from the updater.

Regards,
Dave

[DWMX 2004]|[FlashMX 2004 Pro]|[Studio MX 2004]|[SQL]|[Access2000/2002]|[ASP/VBScript]|[XP-Pro]
If you like online gaming, please register @ www.nova-multigaming.com

Hi Ultradav,

yep, it was an act of recklessness. And i regret it deerly!

So yesterday evening i decided to reinstall (for the fifth time). And suddenly my hand stopped at the DMX 6 CD. So i installed that one. Curious to see how that works out.

I am even more curious to hear from other people how they are faring with DMX for ASP-development.

The client is allways right even if he is not.

My copy is sitting in a software cupboard and that is where it will stay...

I went through loads of grief moving from Ultradev 3 to MX...but I got over it as MX was a great product update.

Then I got MX 2004 ... I did like the CCS changes in MX 2004 but not worth the grief it gave me every single day....so it is now off and off for good until Macromedia come up with some fixes. I have returned to my happy world of MX Studio, sad when you think how much it costs.

Regards
Vince

Visit my home: www.chez-vince.com

VBScript | ASP | HTML | SQL | Oracle | Hosting

very sad to be quite frank.

Regards,
Dave

[DWMX 2004]|[FlashMX 2004 Pro]|[Studio MX 2004]|[SQL]|[Access2000/2002]|[ASP/VBScript]|[XP-Pro]
If you like online gaming, please register @ www.nova-multigaming.com

I've been using DMX 2004 for quite some time now... and so far, the only problem i'm having is when i try click Live Data View, when m connecting a MySQL database to dremweaver mx 2004... I followed the tutorial of Macromedia to the word, I installed and created a database in MySQL correctly...

here's my set-up:

Win2K AS, IIS... I'm using the latest version of PHP and MySQL...

when i test the connection in DMX 2004, it's successful, but when i click on Live Data View, an error occurs, saying that the testing database server (MySQL) is not running, etc.

Funny thing is, i tested that same tutorial using Dreamweaver MX only, and it works...

what gives? any news on an update? or is it really a bug?

There's no such thing as right or wrong; there's what we do, and what we don't do...

MX2004 appears to have more bugs than a disney film.....

Find the box it came in, put the disk in the box, place the box somewhere you cant get at it, re-install MX and wait for Macromedia to come up with some sort of pesticide that will work...

Regards
Vince

DMX Talkzone Manager

Visit my home: www.chez-vince.com
(Now completely CSS based and bye bye to all tables!)

VBScript | ASP | HTML | CSS | SQL | Oracle | Hosting

Hi, reversed the whole thing to MX (6.1).
Works now.

----------------------------------------------
The client is allways right even if he is not.