Previously ran a Foxpro 2.5 dos application on a Win95 machine with no problems. Now I need to create a zenworks application object shortcut to the server application for a Win nt 4.0 w/sp3 machine. When I do this and run the shortcut (which also loads the program the user requires via the prg) I get the message "too many memory variables". I'm not a foxpro programmer - just trying to create the zen shortcut. Any ideas on what to do next.
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 Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
memory variables error 1
- Thread starter svoight
- Start date
-
1
- #2
In the original shortcut, you probably had a command line switch something like "-cc:\FPDApp\config.fp". This points the application at a configuration file (a plain ASCII text file that can be opened in Notepad). In this file there was probably a line that looked like this:
MVCOUNT=800
The default value for the Memory Variable COUNT for FPD is just 512 (note: I'm guessing at the 800 - it could be higher).
This CONFIG.FP file may have other "critical" values in it like:
MEMLIMIT=
DEFAULT=
PATH=
RESOURCE=
HELP=
TMPFILES=
Rick
MVCOUNT=800
The default value for the Memory Variable COUNT for FPD is just 512 (note: I'm guessing at the 800 - it could be higher).
This CONFIG.FP file may have other "critical" values in it like:
MEMLIMIT=
DEFAULT=
PATH=
RESOURCE=
HELP=
TMPFILES=
Rick
ChrisCarroll
Programmer
- Oct 10, 2000
- 177
or, as a PS to Rick, your original setup was able for some other reason to find config.fp, whereas your Zenworks shortcut will most easily be able to find it by making sure that the config.fp file is in the startup directory.
Chris,
Good catch. In addition FPD looks for an Enviroment variable - FOXPROCFG, if it exists, it will use that.
From the FPD help file:
CONFIG.FP
---------
FoxPro allows you to modify file storage locations and initial SET command defaults with a configuration file named CONFIG.FP.
When FoxPro is started, it automatically searches the current working directory for a CONFIG.FP file. If one isn't found, FoxPro searches the FoxPro directory and finally the MS-DOS path for CONFIG.FP. (Your MS-DOS manual provides a description of how to set a MS-DOS PATH.) If no CONFIG.FP file is found, FoxPro's default settings are used.
When you start FoxPro, you can include an optional switch to specify the name of the configuration file to be used:
FOXPRO -C<pathname>\<file>
Alternately, you can include the following line in the AUTOEXEC.BAT file to specify a configuration file:
SET FOXPROCFG=<pathname>\<file>
Rick
Good catch. In addition FPD looks for an Enviroment variable - FOXPROCFG, if it exists, it will use that.
From the FPD help file:
CONFIG.FP
---------
FoxPro allows you to modify file storage locations and initial SET command defaults with a configuration file named CONFIG.FP.
When FoxPro is started, it automatically searches the current working directory for a CONFIG.FP file. If one isn't found, FoxPro searches the FoxPro directory and finally the MS-DOS path for CONFIG.FP. (Your MS-DOS manual provides a description of how to set a MS-DOS PATH.) If no CONFIG.FP file is found, FoxPro's default settings are used.
When you start FoxPro, you can include an optional switch to specify the name of the configuration file to be used:
FOXPRO -C<pathname>\<file>
Alternately, you can include the following line in the AUTOEXEC.BAT file to specify a configuration file:
SET FOXPROCFG=<pathname>\<file>
Rick
- Status
Similar threads
