HI, I was hoping for a bit of help....

I've setup a few dnn sites, and create a fair number of custom modules - so far so good...

We have a new requirement to play presentations created in a product called Articulate. The presentations get converted into a series of flash components, and a static HTML page for displaying them. My plan was to create a module in DNN which contains the content of this html page to load the various presentations. The problem comes in that the flash components use relative paths and must be called from a page in the correct folder (from a browser perspective), with the flash components in a subfolder. No problem, I thought, it's just a case of making the browser believe it's opening the page from the path of the presentation, which is simple in that I can do a redirect when the module is first accessed to include the path of where the presenations reside ie /presentationfolder/tabid/333/default.aspx, and the redirect works fine, problem is that the browser thinks it's looking at /presentationfolder/tabid/333/  and for the presenation to work the browser needs to think it's looking at /presentationfolder/. To get around this I can change the redirect to /presentationfolder/default.aspx?tabid=333, and the browser would know it's base is /presentationfolder/ - problem is that as soon as I go to that url something inside dotnetnuke is sending a redirect to /?tabid=333 and I'm losing the /presentationfolder/ path is there anyway to stop this redirect??