Kbase P19380: WHERE clause of query not set correctly
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/06/2005 |
|
Status: Unverified
FACT(s) (Environment):
Dynamics 2.0a
SYMPTOM(s):
WHERE clause of query not set correctly
A dynlookup forms an incorrect query when there is an outer join
involving two tables, this results in no records being listed in the
lookup and so user does not think any records are available.
1. Connect to Dynsports
2. Generate dynamic sdo for table: arm_salesrep
3. Build dynamic sdv based on this sdo with field arm_salesrep.salesrep_name 4. Add fill-in fiChar to viewer
5. Make the salesrep_name a dynlookup with following properties:
basequery:
for each arm_customer no-lock, each gsm_login_company of arm_customer
outer-join no-lock indexed-reposition
browsefields: customer_code, customer_name (linked to fiChar) amd
customer_discount
displayed field: customer_discount
6. Build a container with standardtoolbar, viewer and fullo with standard
links
7. Run the container and enter 5% in the discount field and press the
binoculars - no records are displayed in the lookup though there are
records with 5%
8. Click the query complete toggle to see the query being executed:
for each arm_customer WHERE (arm_customer.customer_discount >= '5%')
no-lock,
each gsm_login_company of arm_customer WHERE
(arm_customer.customer_discount <= '5%') outer-join no-lock
indexed-reposition
9. Go to the filter tab and enter 5 in the From/To fields for the
discount and then press Apply, return to the Lookup tab and all 5%
records are displayed.
10. Press the query complete toggle and note the query now reads:
for each arm_customer where (arm_customer.customer_discount >= '5' and
arm_customer.customer_discount <= '5') no-lock,
each gsm_login_company of arm_customer outer-join no-lock
indexed-reposition
CAUSE:
Bug# 20030214-003
FIX:
Upgrade to Dynamics V2.0 Service Pack 02.