ALWAYS SAVE YOUR VERSION OF A PUBLIC QUERY WITH A UNIQUE NAME – RECOMMEND USING THE CREATOR’S INITIALS AS FIRST THREE LETTERS OF NAME. PLEASE REVIEW PUBLIC QUERIES TO CONFIRM THAT YOUR INITIALS DO NOT DUPLICATE THE FIRST THREE LETTERS OF AN EXISTING QUERY. IF YOUR INITIALS HAVE ALREADY BEEN USED, PLEASE USE A NEW UNIQUE COMBINATION AT THE BEGINNING OF YOUR QUERY NAME. (DURING IMPLEMENTATION, SAVE ALL QUERIES, BOTH PUBLIC & PRIVATE, ON GIBRALTER & TITANIC IN 003 HULLIHEN HALL WITH YOUR INITIALS).

Problems with saving public and private queries with same name:

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

One situation arises when you have created both a private and a public query with the same name, but the queries are not identical.

When you run a query with a duplicate name, the query on your screen may not be the actual query that is run depending on whether you run to the screen or to Excel.

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

Query/Crystal 7.5 - If you have a public query and a private query with the same name and you try to run one of those queries to crystal you will get a PSQED Application Error.

RESOLUTION - This is a bug, incident T-MEAVES-3L5LA has been opened to address this issue, 5/11/99.

EXPLANATION - Development is aware that this is a problem but they won't be fixing it, instead they are going to not allow a user to save a public query and private query with the same name in future releases. This change is targeted for release 9. Until then, users should not name private and public queries with the same name.

WORKAROUND - Rename one of the queries so that there is not a public and a private query with the same name.