Prompting twice

[Guest]

A query only has one user prompt; but when run, it prompts the user twice to
enter the same information. How do I get it to only prompt once? Any help
would be greatly appreciated!

Linda

 

[Guest]

Can you post the SQL?

 

[Guest]

It happens on most of our queries, but here's an example:

SELECT LDY_N_IN2_ITEM_CROSS_REFERENCES.CROSS_REFERENCE,
LDY_N_IN2_ITEM_CROSS_REFERENCES.CROSS_REFERENCE_TYPE,
LDY_N_IN2_ITEM_CROSS_REFERENCES.[ITEM$NS_ITEMS],
LDY_N_IN2_ITEM_CROSS_REFERENCES.ITEM_DESCRIPTION,
LDY_N_IN2_ITEM_CROSS_REFERENCES.ORGANIZATION
FROM LDY_N_IN2_ITEM_CROSS_REFERENCES
GROUP BY LDY_N_IN2_ITEM_CROSS_REFERENCES.CROSS_REFERENCE,
LDY_N_IN2_ITEM_CROSS_REFERENCES.CROSS_REFERENCE_TYPE,
LDY_N_IN2_ITEM_CROSS_REFERENCES.[ITEM$NS_ITEMS],
LDY_N_IN2_ITEM_CROSS_REFERENCES.ITEM_DESCRIPTION,
LDY_N_IN2_ITEM_CROSS_REFERENCES.ORGANIZATION
HAVING (((LDY_N_IN2_ITEM_CROSS_REFERENCES.CROSS_REFERENCE) Like "*" & [Cross
reference number?] & "*"))
ORDER BY LDY_N_IN2_ITEM_CROSS_REFERENCES.ORGANIZATION;

Another programmer and I have the same problem with most of our queries. We
think it may have something to do with the fact that we are querying ODBC
linked Oracle tables, but haven't been able to figure out why or correct it.
Any ideas? Thanks for the feedback!

Linda

 

[MGFoster]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Multiple prompts on a query means you've filtered the query and then
saved the query w/ that filter(s). For each filter/sort the query will
prompt you for the criteria again. To cure this: run the query & then
right click on the query and select Remove Filter/Sort then save the
query & click Yes when prompted to save changes to the query.
--
MGFoster:::mgf00 <at> earthlink <decimal-point> net
Oakland, CA (USA)

-----BEGIN PGP SIGNATURE-----
Version: PGP for Personal Privacy 5.0
Charset: noconv

iQA/AwUBQ8wRJoechKqOuFEgEQLImQCglCooMZZcIoMlVxWvlmaQ6DxJnFUAoNcE
GuZpdWphS+KIR+0vtG8x3Cat
=h1bn
-----END PGP SIGNATURE-----

It happens on most of our queries, but here's an example:

SELECT LDY_N_IN2_ITEM_CROSS_REFERENCES.CROSS_REFERENCE,
LDY_N_IN2_ITEM_CROSS_REFERENCES.CROSS_REFERENCE_TYPE,
LDY_N_IN2_ITEM_CROSS_REFERENCES.[ITEM$NS_ITEMS],
LDY_N_IN2_ITEM_CROSS_REFERENCES.ITEM_DESCRIPTION,
LDY_N_IN2_ITEM_CROSS_REFERENCES.ORGANIZATION
FROM LDY_N_IN2_ITEM_CROSS_REFERENCES
GROUP BY LDY_N_IN2_ITEM_CROSS_REFERENCES.CROSS_REFERENCE,
LDY_N_IN2_ITEM_CROSS_REFERENCES.CROSS_REFERENCE_TYPE,
LDY_N_IN2_ITEM_CROSS_REFERENCES.[ITEM$NS_ITEMS],
LDY_N_IN2_ITEM_CROSS_REFERENCES.ITEM_DESCRIPTION,
LDY_N_IN2_ITEM_CROSS_REFERENCES.ORGANIZATION
HAVING (((LDY_N_IN2_ITEM_CROSS_REFERENCES.CROSS_REFERENCE) Like "*" & [Cross
reference number?] & "*"))
ORDER BY LDY_N_IN2_ITEM_CROSS_REFERENCES.ORGANIZATION;

Another programmer and I have the same problem with most of our queries. We
think it may have something to do with the fact that we are querying ODBC
linked Oracle tables, but haven't been able to figure out why or correct it.
Any ideas? Thanks for the feedback!

Linda

:

Can you post the SQL?

--
\\// Live Long and Prosper \\//
BS"D


: