Tim - Good work on the custom sql admin report. I was thinking that the Partners may find this helpful as an alternative to PHPMyAdmin (as mentioned in the forums). One thing that I think would improve things would be to require confirmation before defining (not necessarily for each execution) if there is risk of it modifying the database. I think anything with an UPDATE, EMPTY, DROP, or INSERT should be suspect. As a worse case scenario, I imagine someone reading on some blog that some DROP or EMPTY is a good idea and they add it without understanding what it does. At least a confirmation warning would alert an admin that they were creating a potentially dangerous and irreversible activity such that they should have a good backup of the database. Peace - Anthony

p.s. - I took the leading spaces out of the component name in the tracker so it is now alphabetical and set all issues to be assigned to the component lead (you) rather than the project lead (me). Thanks for covering the bases (tracker, CVS, download, M&P, and forum).