Debugger Out of Memory: Pdox7 for Win 3.1 
Author Message
 Debugger Out of Memory: Pdox7 for Win 3.1

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{*filter*} 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 !



Thu, 26 Nov 1998 03:00:00 GMT
 Debugger Out of Memory: Pdox7 for Win 3.1


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{*filter*} 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 !

Check out compileInformation in the online help.  Put the code in a
button on your form and run it, and see how close you are to the 64k
code limit per form.

The de{*filter*} 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{*filter*}.

This applies to 16 bit versions of Paradox only.

Andrew
--
  Andrew Bennett

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



Thu, 26 Nov 1998 03:00:00 GMT
 Debugger Out of Memory: Pdox7 for Win 3.1

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



Sat, 28 Nov 1998 03:00:00 GMT
 Debugger Out of Memory: Pdox7 for Win 3.1

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{*filter*} 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 am not the least bit suprised.  The amount of RAM in the machine is
irrelevant to the problem that you have which is poor design.  Get that
code out of the form and into one or more libraries.  PdoxWin forms
and libraries can not be unlimited size.  This has nothing to do with
PdoxWin and everything to do with Windows resources.

Daniel Morgan
EXE Solutions



Sat, 28 Nov 1998 03:00:00 GMT
 
 [ 4 post ] 

 Relevant Pages 

1. Formatted Fields Pdox7 Win 3.1

2. Graph Disapears Pdox7 Win 3.1

3. Changing Open Order-Forms Pdox7 Win 3.1

4. Lost Clusters Pdox7 Win 3.1

5. Restructuring an existing database in PDOX7 for Win 3.1

6. Using Debugger in a library method: Pdox 7 for Win 3.1

7. HELP!!Win 3.1 Client <==>Win NT Sql Server

8. VB3 program OK in WIn 3.1 but not in WIN 95

9. Creating Win 3.1 apps/network apps in win 95

10. Pdox 5 and Win 3.1/locate producing win error

11. transfer files from Win 3.1 to Win 98


 
Powered by phpBB® Forum Software