Kbase P4398: Bad SQL Occurs when WHERE Clause Involves a Logical Field wi
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
05/02/2003 |
|
Status: Unverified
FACT(s) (Environment):
Progress 9.1C
FACT(s) (Environment):
SQL Server 2000
SYMPTOM(s):
Bad SQL is generated when setting a variable against a logical field with extents.
S0022: [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name
'month_quota'.
S0022: [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name '##5'.
S0022: [Microsoft][ODBC SQL Server Driver][SQL Server]Statement(s) could not be
prepared.
20011030-014- Wrong SQL logical fields - MSS
CAUSE:
The issue occurs when running a query using a logical field on the WHERE clause without saying = no, or = yes.
def var x as int initial 1.
for first test where a[x].
end.
FIX:
The following is a workaround.
Change the query to say; changed to explicity say
a[x] = yes or a[x] = no