[Elaine Tucker]

vote now

I'm a little confused by the first option -- I thought you COULD overwrite an existing query using an output query.

[Elaine Tucker]

Per Drew's Post 8-23-06 on "The List":

Here is the problem. I have a process where I create an output query and then use the output query in and export. Currently, if I create an output query with the same name as an existing one, it deletes the current query and createws a new query with the same Name but a DIFFERENT query ID. When I go to run the export, the query that it was using is NO LONGER AVAILABLE, so I have to go in and select the new output query

Couldn't that be considered a good feature, in that it warns you that the query your export was using has changed? (That's the way I've always looked at it.) Granted, it is an inconvenience.

[DrewAllen]

Quote:

Originally Posted by Walter Koenig

Couldn't that be considered a good feature, in that it warns you that the query your export was using has changed? (That's the way I've always looked at it.) Granted, it is an inconvenience.

What I would like to see is a couple of options when there is an existing query with that name:

1. Choose another query name.
2. Overwrite the existing query (keeping the same query ID).
3. Replace the existing query (changing the query ID).
4. Search for dependencies. (Look for queries, exports, and reports that use that query.)

RE already has some of this functionality with Exports. It will tell you that an export is used with a custom report. It should be able to do the same thing with Queries, but still allow you to replace it.

Drew