Kbase 15344: Error 560 with shared browse running from UIB in 7.3B and up
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
Error 560 with shared browse running from UIB in 7.3B and up
Why do I see error 560 in the UIB?
----------------------------------
You may encounter error 560 when you RUN or SAVE your
.w in the 7.3B UIB if you are implementing a shared browse
with a customized join.
THis error happens only in the UIB at these times because
the UIB has a bug in it that produces an incorrect
'open query' statement. The incorrect 'open query' statement
has several underscores in it and omits the 'dbname_' before
each table name reference.
The workaround
--------------
The workaround is to go into the property sheet of the browse,
and check OFF the 'open query' attribute. Now, put your own
syntactically correct 'open query' statement after the
call to enable_ui in the main block. By avoiding using
the UIB-generated open query statement, you will get
correct results. You will however NOT avoid the error 560
when saving or running code in the UIB. These errors will
only be seen by the application developer who is using the
UIB to maintain his application. It is an inconvenience to
the developer but will not affect the end user in any way.
You must press the OK button for each error 560 that is
displayed but when that is done, you will see your browse
with the correct results in it.
At this time, there is no way to avoid these errors in the
version 7.3 when saving or running this
particular type of code from the UIB.
Note: If you are running this type of code in later versions
of the UIB (for example, version 8) and you originally
created this code in the 7.3B UIB, then you will still see
these errors.
What is this particular type of code?
-------------------------------------
The 'bad' code is generated when you create a browse,
turn ON 'shared' attribute in the property sheet, and
do a join between 2 tables using a WHERE clause and not
just the OF clause. WHen you SAVE or RUN this code from
The UIB, the UIB produces error 560 and a syntactically
incorrect open query statement is generated. You can look at
it in the code preview or procedure editor to see this.
Progress Software Technical Support Note # 15344