At some point you have to create a DNN module. It's the only thing DNN knows how to manage, so it's the only way to get your code on a page.

That module can happily call/use any .Net code you like including using non-DNN ascx's, and using DB's that DNN does not know about.

It's an approach I use. The only downsides I see are:
- you have to co-ordinate backing up multiple databases
- any transactions in the DB's are not co-ordinated (they could be if you are happy to use distributed transactions, but I don't need that in my case).

---

Best wishes,
- Richard
Agile Development Consultant, Practitioner, and Trainer
www.dynamisys.co.uk