Sorry - I didn't explain that as well as I should have. I'm not suggesting that you use TheStone's "template dumper" code, I'm suggesting that you create a file called Custom.pm (or whatever.pm) and put it in /admin/Dbsql. Then you can write custom perl sub routines using the GT libs that access other tables in your database. I have used this technique extensively on a site that uses over 80 different tables in DBManSQL, and it works beautifully, often accessing 5-6 different tables on the same page. You do need to be comfortable with a little basic perl programming, of course. If you decide to go this route, I would also suggest that you spend some time reading through the GT Module documentation, which you can access by clicking the "Help" link in your admin panel.

In any event, the way you would use this in a template is as follows. Say you put a subroutine called "doTheThing" in a new module called "Custom.pm". You could call that subroutine from any template in your setup by using <%Dbsql::Custom::doTheThing%>. If you write a subroutine that can have args passed to it, then you would use <%Dbsql::Custom::doTheThing($arg1, $arg2, etc.)%>

I hope that helps. I admit, this approach may be a little advanced for a new user without much perl experience. But like I said, I've had great success with it, and I'm a crappy programmer with VERY little perl knowledge. Once you get the hang of it, it's a great way to extend the functionality of DBMan SQL.

---

Fractured Atlas :: Liberate the Artist
Services: Healthcare, Fiscal Sponsorship, Marketing, Education, The Emerging Artists Fund