I use a database program which has worked perfectly for years on win 3.1 and win 95 on or off a network on pentium one with modest memory. When I loaded Foxprow on a Win 98SE (or on newer computer which has bigger memory) it begins to run OK but as soon as I require it to find one record of a 500 record DB it comes with "out of memory error" andyou cannot work on it anymore. Same if you try and use FILER to look for something. Itried fiddling with memlimit but failed, how do I cure this anyone please?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Foxprow 2.6 works "out of memory" on win 98/xp 1
- Thread starter interbabe
- Start date
-
1
- #2
Previously, I would have recommended you to read "Insufficient Memory in FoxPro for Windows on Fast Computers", at - unfortunately MS killed this article off early in 2000 (they really don't want to support FPW any more). [See Article quoted below thanks to Cindy].
While some or the problems can't be fixed (Filer e.g.), there are workarounds for most of the others. e.g. The listbox problem can be fixed, in some cases, by using the ideas in Paul Lee's FPWListBox file at
Rick
"Cindy Winegarden" wrote in message news:3a69955c@news.devx.com...
Here's the text of the article:
-------------
PRB: Insufficient Memory in FoxPro for Windows on Fast Computers
Last reviewed: January 8, 1998
Article ID: Q171047
The information in this article applies to:
Microsoft FoxPro for Windows, versions 2.6 & 2.6a
SYMPTOMS
Working programs in FoxPro 2.x fail with "Insufficient Memory" when run on
newer, faster computers with clock speeds greater than 150 MHz. This problem
applies to both screens with list boxes and queries, but this article
addresses only the problem with FoxPro screens.
The "Insufficient Memory" error message may also occur while in Filer when
changing to a local(not network) directory which contains a large number of
files.
The failure also happens on both MMX and non MMX Computers. The operating
system could be Windows 3.x, Windows for Workgroups 3.x, Windows 95 or
Windows NT. This error does not occur in FoxPro For MS-Dos.
CAUSE
The current fast computers were not available for testing when FoxPro 2.x
for Windows was initially released. Microsoft FoxPro for Windows, 2.x does
not always work with list boxes populated from tables with more than 600
records.
RESOLUTION
At this time Microsoft does not have a good workaround; however, the
following are options to consider:
Upgrade the application to Visual FoxPro 3.0 or 5.0.
Turn off either CMOS cache (slow) or CMOS turbo mode (very slow).
Reduce the number of records to be displayed in the ListBox (under 600).
Run the FoxPro applications (app) and executables (exe) on a slower
computer.
Using an array as the source of the list items in the list box is the best
resolution for this problem. To change the screen created in the Steps to
Reproduce Behavior section below, follow these steps.
a. In the Setup Code for the screen, add the following command:
COPY TO ARRAY aTableField FIELDS charval
b. Double click the listbox on the screen while in design mode.
In the List dialog box that appears, change the List Items to
From Array and put aTableField in for the array name. Choose Ok.
c. Save and generate the screen.
d. Although this shouldn't be necessary, it has been reported that
the array needs to be released when the screen is closed. To do
this, add the following command to the Cleanup Code of the screen:
RELEASE ALL LIKE aTableField
Along with the steps listed above, some users have found that adding the
following line to the Config.fpw file helps to solve the problem:
MEMLIMIT = 60,2048,4098
STATUS
Microsoft is researching this problem and will post new information here in
the Microsoft Knowledge Base, as it becomes available.
MORE INFORMATION
Use the Microsoft Knowledge Base at to
troubleshoot other potential causes of "Insufficient memory" errors. Verify
that the error is due to the processor speed by trying the code on both a
fast and slow computer.
Steps to Reproduce Behavior
The following is a reproducible case where FoxPro for Windows 2.x fails with
"Insufficient memory" with a list box on a screen.
Place the following code in a new program file. Save it as LarTable.prg:
* Sample code to create and populate a large table to test your
* program.
* Environment area.
CLEAR
CLOSE DATABASES
CLEAR SCREEN
* Create a large table
CREATE TABLE LarTable (CharVal C(20), NumVal N(9))
USE LarTable.DBF
* NumRecords = the number of record to be put in the table.
NumRecords= 2000
* Note using larger numbers can take a long time.
NumWide = LEN(ALLTRIM(STR(NumRecords)))
* FOR LOOP to fill the table.
FOR x = 1 TO NumRecords
CharString="Record" + ;
PADL(ALLTRIM(STR(x,numwide,0)),NumWide,"0"
INSERT INTO LarTable (CharVal,NumVal) VALUES(CharString, x)
? RECNO()
ENDFOR
CREATE SCREEN LarTable.scx NOWAIT
Add a ListBox object from the toolbar on the left of the screen.
Select the "From Field" radio button and type LarTable.Charval in the Field
dialog box.
Type "MyList" in the Variable text box. Click OK to close the dialog box.
Resize the ListBox, if necessary.
Add a Push Button. Use "Close" as the prompt, Check the "Terminate READ on
Selection" check box. Enter "xyz" for the variable.
Generate and run the LarTable.spr screen. It should run without error on
computers slower than a 166 MHz computer.
It should fail with an "Insufficient Memory" error on most computers 166 MHZ
or faster. Use "mybutton" as the variable prompt.
The code generally fails when the screen loads on faster machines. This
problem happens only when the table contains more than about 600 records.
Try deleting all but the first 600 records:
DELETE ALL FOR RECNO > 600
(c) Microsoft Corporation 1997, All Rights Reserved. Contributions by Mike
Fernald, Microsoft Corporation
-------------------
While some or the problems can't be fixed (Filer e.g.), there are workarounds for most of the others. e.g. The listbox problem can be fixed, in some cases, by using the ideas in Paul Lee's FPWListBox file at
Rick
"Cindy Winegarden" wrote in message news:3a69955c@news.devx.com...
Here's the text of the article:
-------------
PRB: Insufficient Memory in FoxPro for Windows on Fast Computers
Last reviewed: January 8, 1998
Article ID: Q171047
The information in this article applies to:
Microsoft FoxPro for Windows, versions 2.6 & 2.6a
SYMPTOMS
Working programs in FoxPro 2.x fail with "Insufficient Memory" when run on
newer, faster computers with clock speeds greater than 150 MHz. This problem
applies to both screens with list boxes and queries, but this article
addresses only the problem with FoxPro screens.
The "Insufficient Memory" error message may also occur while in Filer when
changing to a local(not network) directory which contains a large number of
files.
The failure also happens on both MMX and non MMX Computers. The operating
system could be Windows 3.x, Windows for Workgroups 3.x, Windows 95 or
Windows NT. This error does not occur in FoxPro For MS-Dos.
CAUSE
The current fast computers were not available for testing when FoxPro 2.x
for Windows was initially released. Microsoft FoxPro for Windows, 2.x does
not always work with list boxes populated from tables with more than 600
records.
RESOLUTION
At this time Microsoft does not have a good workaround; however, the
following are options to consider:
Upgrade the application to Visual FoxPro 3.0 or 5.0.
Turn off either CMOS cache (slow) or CMOS turbo mode (very slow).
Reduce the number of records to be displayed in the ListBox (under 600).
Run the FoxPro applications (app) and executables (exe) on a slower
computer.
Using an array as the source of the list items in the list box is the best
resolution for this problem. To change the screen created in the Steps to
Reproduce Behavior section below, follow these steps.
a. In the Setup Code for the screen, add the following command:
COPY TO ARRAY aTableField FIELDS charval
b. Double click the listbox on the screen while in design mode.
In the List dialog box that appears, change the List Items to
From Array and put aTableField in for the array name. Choose Ok.
c. Save and generate the screen.
d. Although this shouldn't be necessary, it has been reported that
the array needs to be released when the screen is closed. To do
this, add the following command to the Cleanup Code of the screen:
RELEASE ALL LIKE aTableField
Along with the steps listed above, some users have found that adding the
following line to the Config.fpw file helps to solve the problem:
MEMLIMIT = 60,2048,4098
STATUS
Microsoft is researching this problem and will post new information here in
the Microsoft Knowledge Base, as it becomes available.
MORE INFORMATION
Use the Microsoft Knowledge Base at to
troubleshoot other potential causes of "Insufficient memory" errors. Verify
that the error is due to the processor speed by trying the code on both a
fast and slow computer.
Steps to Reproduce Behavior
The following is a reproducible case where FoxPro for Windows 2.x fails with
"Insufficient memory" with a list box on a screen.
Place the following code in a new program file. Save it as LarTable.prg:
* Sample code to create and populate a large table to test your
* program.
* Environment area.
CLEAR
CLOSE DATABASES
CLEAR SCREEN
* Create a large table
CREATE TABLE LarTable (CharVal C(20), NumVal N(9))
USE LarTable.DBF
* NumRecords = the number of record to be put in the table.
NumRecords= 2000
* Note using larger numbers can take a long time.
NumWide = LEN(ALLTRIM(STR(NumRecords)))
* FOR LOOP to fill the table.
FOR x = 1 TO NumRecords
CharString="Record" + ;
PADL(ALLTRIM(STR(x,numwide,0)),NumWide,"0"
INSERT INTO LarTable (CharVal,NumVal) VALUES(CharString, x)
? RECNO()
ENDFOR
CREATE SCREEN LarTable.scx NOWAIT
Add a ListBox object from the toolbar on the left of the screen.
Select the "From Field" radio button and type LarTable.Charval in the Field
dialog box.
Type "MyList" in the Variable text box. Click OK to close the dialog box.
Resize the ListBox, if necessary.
Add a Push Button. Use "Close" as the prompt, Check the "Terminate READ on
Selection" check box. Enter "xyz" for the variable.
Generate and run the LarTable.spr screen. It should run without error on
computers slower than a 166 MHz computer.
It should fail with an "Insufficient Memory" error on most computers 166 MHZ
or faster. Use "mybutton" as the variable prompt.
The code generally fails when the screen loads on faster machines. This
problem happens only when the table contains more than about 600 records.
Try deleting all but the first 600 records:
DELETE ALL FOR RECNO > 600
(c) Microsoft Corporation 1997, All Rights Reserved. Contributions by Mike
Fernald, Microsoft Corporation
-------------------
- Status
Similar threads
- Locked
- Question
