Kbase 16793: Known Bugs with Actuate Developer Workbench 2.0.10 Beta
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
Known Bugs with Actuate Developer Workbench 2.0.10 Beta
There are few known problems with the Actuate Developer Workbench
2.0.10 beta. All these bugs will be fixed for the final release.
* Lock Table Entries - If an error occurs while a report is
running, it may be because there are not enough entries defined
for the record locking table.Increase the number of entries for
the lock table using the -L databases connection parameter on
the command line that starts the server. (For the details of
setting this parameter, see Chapter 4 of the Progress System
Administration Reference.)
* Make sure that the following DLLs exist on the client machine:
MFC40.DLL, MSVCR40D.DLL, and MFCO40D.DLL. If they are missing
from the client computer, copy them from the directory
\ACTUATE\DLLS\DLL32 on the CD. These should be located somewhere
on your path or in your systems directory.
* The auto join feature does not always join some columns as
expected when the auto joins feature is turned on.
* The performance of various query builder and DB browser
operations is slow when the auto joins feature is turned on.
* A nested group-by in a sub report produces an error message about
the key property even though it is set correctly.
* There is an interim naming scheme in place in the query builder
for array references to avoid conflict with the bracket syntax
for value expressions.
* There is an intermittent case where use of static parameters
results in a crash. Use of adhoc parameters is a good work around.
* Array cells cannot be used as static parameters.
Progress Software Technical Support Note # 16793