Kbase P22850: Parts of where clause disappear using assignQuerySelection.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
25/06/2003 |
|
Status: Unverified
FACT(s) (Environment):
Dynamics 2.0A
FACT(s) (Environment):
Progress 9.1D
SYMPTOM(s):
assignQuerySelection is not working
The assignQuerySelection where clause gets corrupted
Each time it is run, parts of the where clause disappear
CAUSE:
Bug# 20030407-024 which was DUP of Bug# 20030219012
CAUSE:
The problem was only duplicatable in Dynamic data objects. It was due to the fact that the Appbuilder stores chr(10) in the BaseQuery as line breaks whenever the query is large. This will of course disapper when the query is in the source code with a static data object.
This caused a problem in the whereClauseBuffer function that used spaces as tokens/delimiters to find the the table in a query expression and the buffer name were returned with an invisible CHR(10) at the end, which was unrrecognizable when compared to the object's buffer.
It is perhaps questionable to store CHR(10) in the query, but since the 4GL are query object is able to deal with it the SDO should also handle it.
FIX:
Upgrade to Dynamics 2.0A Service Pack 2