Fox for windows 2.6a Windows NT4.0 Setup

[JGB]

I Have an existing system running on a Windows NT 4.0 workstations and Servers with current SP on both. The system is currently working. I have been asked to look at if we can "Tune" the foxpro setup used with it to improve performance. We are currenltly rewriting the system so upgrading to a new version of Fox for this is out. I wasn't sure if anyone has played with the settings in the fp files or config.nt autoexec.nt files to improve anything or had any other ideas. I'm not sure its realistic to expect to be able to do much this way but Its not mine to reason why mine is just to do or die(or something like that). I didn't see anything related to this in the forum so I figure there must not be much you can do with this.

Thanks for the help
Jim

 

[rajeevnandanmishra]

Hi there,
To which version are you upgrading your code? And what performance exactly they asked you to do?

 

[JGB]

We are working on re-writing it using the .net suite of programs not in fox. I was asked to look at how we have fox and this application setup to see if we can improve over all speed. I know that isn't a very specific answer. We have specific code we are looking at to fix bottle necks in the process mostly filters and sql statements that need tuning. I was asked to look at this to see if anything in the setup was causing over all performance loss.

Thanks
Jim

 

[rajeevnandanmishra]

Hi,
Hmm.., Generally developer put the path entries in FP file.
SET Like TMPFILES=c:\temp
These are generally put to increase the perormance.
Now, I don't remember what other options can be put there for performance.

 

[JGB]

Thanks for the hint. If you have any other ideas I'd appreciate it.

Thanks
Jim

 

[NathanGriffiths]

Hi,
These tips are from an old MS support document on optimizing FoxPro for a network for all versions 2.5 - 6.0

1. Install local copies of FoxPro on the workstations and only have data that needs to be shared on the network.

2. Create a local Config.fpw for each node or workstation. Force FoxPro (or EXE's written in FoxPro) to find and use the specified local configuration file. The proper syntax to specify a configuration file is shown below:

-C<path>

For example, to ensure that FoxPro uses a specific config.fpw file modify the command line of the startup icon or program to look like the following:

c:\apps\customer.exe -cc:\temp\config.fpw

Note: Ensure that there is no space following the -c parameter. Also if the subdirectory name includes a space you must enclose the entire -c parameter within double quotes.


4. Make sure all temporary files and work files are located on the local drive. For example, the Config.fp file (or, in the Windows product, the Config.fpw file) would contain the following entries:

tmpfiles = c:\foxtemp
sortwork = c:\foxtemp
progwork = c:\foxtemp
editwork = c:\foxtemp

Note: Ensure it is a valid, existing subdirectory on local drive.


Within the configuration file, specify a local resource file. By default the name of the resource file is Foxuser.dbf and there is an assocated Foxuser.fpt file. It is a normal FoxPro table. For example, the Config.fpw file would contain the following entry:

resource=c:\apps\myuser.dbf

5. If there are files that need to be shared but are rarely updated (an example would be States.dbf, which has state abbreviations and full names), mark those files with the Read-Only attribute at the network level. For example, to mark States.dbf as read-only on a Novell network, you would type:

FLAG states.dbf +RO

States.dbf will now open faster.

Hope some of this helps,

Nathan