Kbase 8785: 63K limit exceeded when compiling RESULTS query form
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
63K limit exceeded when compiling RESULTS query form
910626-jom01
INTRODUCTION:
=============
This Product Services Technical Support Knowledgebase entry
describes the 63K limit when compiling Results Query Forms.
WHY YOU NEED TO DO THIS:
========================
When Progress compiles a query form and the resulting code exceeds
63K, the system will return a fatal error. This may happen during the
Initial Build or when you try to add an Individual Form.
PROCEDURAL APPROACH:
====================
Reasons for this Error:
- R-code dependent on the number of fields in form. It does not
matter if these fields are referenced or not.
- Large validation expressions generate lots of r-code.
- Likewise for help messages and/or validation messages.
- Use of Decimal fields can geneate overheads in r-code.
- Complicated forms and/or long labels.
- Long formats in data types.
Workarounds:
The Obvious:
- Try not to use large validation expressions, large help/
validation messages, decimal fields, long formats.
- Consider breaking up complicated forms into a number of
smaller forms.
The Not So Obvious:
- In Version 5, if you do not need to generate a form for a
particular file, mark the file within the data dictionary
as HIDDEN. Then once you have performed the Inital Build
unhide the file. In Version 6, use the Semi-Automatic build
and don't build a form for it.
- Change the Field Characteristics within Form Definitions of
the Administration Model:
(a) Eliminate ALL Browse fields.
(b) Eliminate ALL Add/Update/Copy fields.
(c) Eliminate ALL Query fields and use the WHERE option instead.
- Consider using one form for Query and a different form for
Add/Update/Copy.
REFERENCES TO WRITTEN DOCUMENTATION:
====================================
SOURCE: RESULTS Technical Support Seminar presented by Tony Lavinio.
Progress Software Technical Support Note # 8785