Originally Said By: Ray Borduin
The ordering of the code issue is only a problem when applying server behaviors individually. Since you apply them one at a time, Dreamweaver doesn't know the correct order you intend. A larger wizard doesn't have that problem because we are able to apply all the server behaviors at once in the correct order instead of asking Dreamweaver to figure out the order when applying them individually. 
Yes, but if you have lots of other code on your page then it's 100% feasible that the wizard could install it before, after or right in the middle of that code thus causing problems. The wizard may well put the WebAssist code in the correct order but you are still at the mercy of Dreamweaver in terms of "weight" by your own account.
Originally Said By: Ray Borduin
You secure the pages with the new MySQLi "Restrict Access to Page" server behavior just like you would with the old Dreamweaver version.
We're using WebAssist SecurityAssist. Does it not have a facility to secure pages after login?
Thank you
NJ
