This is a tricky one I think. I'm building an ASP site using a page which calls dynamic includes with a workaround using a case statement. The dynamic includes work fine, I mean, showing and requesting the data etc. Trouble comes in when I'm trying to use some specific server behaviours, like paging through recordsets and using conditional regions.

Dreamweaver by default inserts the familiar MM_whatever variables. I thought I had a solution to this by replacing the MM_xxxx by a manual code like AB_xxxx and CD_xxxx for the different pages I use, because otherwise the same variable will be defined more then once. This seems to be a problem because Dreamweaver recognises the server behaviours or variables by this MM_xxx.

Before wasting lots of time, I would like to hear some suggestions. Should I define all the recordsets on the index page which calls the includes or do that specifically on the include page? Just a guess. I would really, really appreciate some help on this question, because I already wasted many hours on this.

Problem solved! Dropped D-MX to do it just by handcoding and it works!