Very Computer

I have an application for which the .FSL file runs about 240 Kbytes, and the listing fills more
than sixty pages.  It's a tracking database for custom ic's used in our medical products.

The main form includes about ten buttons, each served by its wad of code.

This is running in a Gateway Pentium with 16 Mbytes of ram.

Any attempt to bring up the de* generates the out of memory error, and shows the spot in
the listing where it ran dry.

Same thing happens in a system with 20 Mbytes of ram.

I had seen this in version 4.5, from which I have just upgraded.

Wondering if this is due to a (modifiable) default parameter, or is it the end of the road ??  

Any clue would be great !

Quote:>I have an application for which the .FSL file runs about 240 Kbytes, and the listing fills more
>than sixty pages.  It's a tracking database for custom ic's used in our medical products.
>The main form includes about ten buttons, each served by its wad of code.
>This is running in a Gateway Pentium with 16 Mbytes of ram.
>Any attempt to bring up the de* generates the out of memory error, and shows the spot in
>the listing where it ran dry.
>Same thing happens in a system with 20 Mbytes of ram.
>I had seen this in version 4.5, from which I have just upgraded.
>Wondering if this is due to a (modifiable) default parameter, or is it the end of the road ??  
>Any clue would be great !

The de* adds overhead to the code limit, somewhere in the
neighborhood of 15-25k.  So, if your form has 40k or more of code, you
could be hitting this limit which doesn't allow you to use the
de*.

This applies to 16 bit versions of Paradox only.

Andrew
--
  Andrew Bennett

  http://www.veryComputer.com/~abennett/

Hello again:

Well, I looked into the situation and, following your advice, found that the compiled code
of my single form ran to nearly 62 Kbytes ... darn close to the 64K form limit !

So I am splitting things out into multiple forms served by a common library, and it feels much
better !

Thanks for pointing me down the right pathway !

Dick

Quote:> I have an application for which the .FSL file runs about 240 Kbytes,
> and the listing fills more than sixty pages.
> Any attempt to bring up the de* generates the out of memory error,
> and shows the spot in the listing where it ran dry.
> Same thing happens in a system with 20 Mbytes of ram.

Daniel Morgan
EXE Solutions