When compiling a bigger form in PDOXW5, compiling procedure starts normaly
but ends suddenly with error message "Not enough memory".
No additional error messages are available.
The form itself is stored succesfully. Size of form before compiling 315 kB,
form described as follows:

26 Data entry fields most with programmed lists
6 push buttons, no table objects
38 methods used (6 integrated, 13 self declared, 19 lib methods)
190 declared variables, 110 declared constants

Could anybody help?

HARD- AND SOFTWARE ENVIRONMENT
PCI-Board, 16 MB RAM, 35 MB perm memory under Windows
557 kB lowmem and 13,3 MB XMS free, no ems  
PCI-graphics adapter Spea V7 MIRAGE with 2 MB on board
Toshiba CD-ROM drive XM 3401 B
DOS 5.0, Windows 3.1, Paradox for Windows 5.0
Recommended settings by Borland in AUTOEXEC.BAT and CONFIG.SYS
-------------------------
Heiko Weier

-------------------------

: When compiling a bigger form in PDOXW5, compiling procedure starts
: normaly : but ends suddenly with error message "Not enough memory".  : No
: additional error messages are available.  : The form itself is stored
: succesfully. Size of form before compiling 315 kB, : form described as
: follows:

: 26 Data entry fields most with programmed lists
: 6 push buttons, no table objects
: 38 methods used (6 integrated, 13 self declared, 19 lib methods)
: 190 declared variables, 110 declared constants

: Could anybody help?

Two suspects:

1) out of user resources

2) out of lower memory

Unfortunately, you need something like Norton System Watch to display
those statuses.

--
+==========================================================================+

| Pretty good Paradox for Windows Programmer                               |
| Self-proclaimed Treknologist                                             |
| Editor XCOM: Unofficial Strategy Guide http://userwww.sfsu.edu/~kschang  |
+==========================================================================+

        If you've got 5.0, use COMPILEINFORMATION (see the help file)
to see how close you are to the limits of forms. Sounds like you're
pretty close.

--
Beavis kicks ASS! He KICKS 'em! Kicks, KICKS!  He rules, he RULES, RULES!!

Sounds to me like you hit the majic 64k barrier better to remove a method a see
if it then redelivers okay.

Bryan Oliver

: : When compiling a bigger form in PDOXW5, compiling procedure starts
: : normaly : but ends suddenly with error message "Not enough memory".  : No
: : additional error messages are available.  : The form itself is stored
: : succesfully. Size of form before compiling 315 kB, : form described as
: : follows:

: : 26 Data entry fields most with programmed lists
: : 6 push buttons, no table objects
: : 38 methods used (6 integrated, 13 self declared, 19 lib methods)
: : 190 declared variables, 110 declared constants

: : Could anybody help?

: Two suspects:

: 1) out of user resources

: 2) out of lower memory

: Unfortunately, you need something like Norton System Watch to display
: those statuses.

: --
: +==========================================================================+

: | Pretty good Paradox for Windows Programmer                               |
: | Self-proclaimed Treknologist                                             |
: | Editor XCOM: Unofficial Strategy Guide http://userwww.sfsu.edu/~kschang  |
: +==========================================================================+

I solved the problem thanks to the help of this forum
by using compileInformation and two additional libraries
interacting with each other.

But I do still not know what the terms code size and data size of
compileInformation represent. They display value changes when
called multiple while a form is running.

And does anybody perhaps know any other way to let the pdoxw5
compiler ignore those 64kB barriers?

Heiko Weier

: I solved the problem thanks to the help of this forum
: by using compileInformation and two additional libraries
: interacting with each other.

: But I do still not know what the terms code size and data size of
: compileInformation represent. They display value changes when
: called multiple while a form is running.

: And does anybody perhaps know any other way to let the pdoxw5
: compiler ignore those 64kB barriers?

Nope, the 64K barrier is built into the compiler.  You'll have to wait
until PDOXWIN 6, or use Delphi.  It's 64K source, 64K stack, and 64K
symbols, if I remember correctly.  (thanks to Bob Lenarcik for the
correction a while back...)

--
+==========================================================================+

| Pretty good Paradox for Windows Programmer                               |
| Self-proclaimed Treknologist                                             |
| Editor XCOM: Unofficial Strategy Guide http://userwww.sfsu.edu/~kschang  |
+==========================================================================+