Umm, okay... technical question here. How exactly does this speed up the site in any meaningful way? It doesn't take hardly anything to draw up a temp query URL for the next 'page', considering that each user will have a unique MySQL sess* file sitting in /tmp anyway. IF they're that strapped for CPU cycles, a query URL construct could be built with a 5-20 second lifetime, then disbursed to any session asking for a page with that URL in it as part of a user page load for the duration of the URL's lifetime. This way you can still have the buttons, but only have to build a pair of URLs for them once every so many seconds, instead of a pair per customer per page request. Is Bondware that much in need of a roll-back and re-write, or is it perhaps that underpowered hardware may be the problem? I'm asking this because if they're having to shave all these tiny nickel-and-dime bits off to scrounge CPU cycles, then the problem has to resolve down to one of those two conditions. /P