Of course, there is always another way to start QA

How about creating an association to a script file extension - I guess most of us use .SQL.  The association can be set via the QA Options - General Tab.  Set "Select SQL Query Analyser as the default editor ... etc" to true.  Then a simple "double-click" of the script file from Windows Explorer initiates the loading of QA.  Make sure you choose the correct database before executing the script.

There is a down side to this if you use an external text editor for creating scripts.  Obviously, that editor will no longer act as the double-click default.  To overcome this, there is always the "open With" option when you right-click a script file.  WinXP will remember this after the first time it is done (you may have to go through selecting a program the first time it is done) so that QA always appears as an option thereafter.

It is also not a great method if you are working with multiple databases/servers.  But for DBAs predominantly working on a single database it certainly provides a fast method of opening QA with the added advantage of already displaying the script you want.

So there you have YAC - yet another choice - just what everyone needs.

Rowan Shattky

--------------

Life is not a chair to sit on, but a cliff to hang from.