Usually (and i meant that in the general sense of the word) the need to add extra components to 'expand' your user interface is an indication that you're doing something wrong.
Yes, I would strongly agree.
I would move your "standard" queries out of the program too. Put them in an .ini file that is installed alongside the program so less likely that it would be messed with.
Display all query descriptions in a list. When the user clicks on a list item, the query is displayed in a TMemo. Have a Run button or whatever it is you're trying to do with the query.
Add a New button that brings up a dialog that prompts for a new query description and query. This is added to list and saved in a second .ini file somewhere in a user-writable part of file system. When program starts it needs to load both .ini files.
Ideally you would have some way of doing a check of syntax on the entered query. Absent that, at least make sure you can recover from any exception raised by a bad query.
Also, how do you prevent a user's query from changing database contents if you don't want that?