I'm not sure why you have resurrected a six-year-old thread. Dreamweaver server behaviors prior to Dreamweaver 8.0.2 (released in 2006) were subject to a serious threat known as SQL injection. The 8.0.2 updater fixed the problem. However, Dreamweaver server behaviors were deprecated and removed from Dreamweaver a couple of years ago.
Why were they deprecated? Dreamweaver's server behaviors rely on a set of functions for connection to MySQL that have been dropped from PHP 7, the next major version of PHP that is scheduled for release in November 2015. The functions were deprecated by PHP in June 2013, and many hosting companies began turning them off in PHP 5.5 and 5.6. Anyone relying on Dreamweaver's server behaviors is living on borrowed time. Even if you decide not to upgrade to PHP 7, official support for PHP 5.6 will end in less than two years' time (August 2017). After that, if you're still running PHP 5, you're running a version of PHP that will never get security updates.
Unfortunately for people who don't want to get involved with hand-coding, Adobe has not updated the server behaviors, nor has it announced plans to do so in future. Although it's possible to adapt the code generated by Dreamweaver, it's actually much simpler to ditch it completely and start from scratch using either MySQL Improved or PDO. Whichever approach you take, it's vital to protect database queries against SQL injection. The safest way to do this is to use prepared statements, which are supported by PDO and MySQLi. If you're using the techniques taught in my book PHP Solutions (2nd or 3rd editions) or my database course on lynda.com, you should be safe.