Rogue config.fpw

[yert33]

Working at a new company. Was given a desktop for development purposes. Installed VFP 9.0 SP1 on it. Started creating an application.

Unbeknownst to me, another FoxPro app had been installed on this machine before I got it. This app had created it's own config.fpw file on the local drive. That config.fpw is as follows:

RESOURCE=C:\OtherAppTemp\FOXUSER.DBF
TMPFILES=C:\OtherAppTemp\
KEYCOMP = WINDOWS
CATMAN=OFF
MVCOUNT=65000
CODEPAGE=437

The codepage line is my concern. In trying to optimize my Select statements with SYS(3054,1) I stumbled across the fact that I had codepage conflicts between some DBF's and some PRG's. So I used CPZERO to change all my tables to 437. But it didn't help my speed issues.

The application will be distributed to machines without this other app installed.

When my app, which has been compiled (W32 exe) in codepage 437, runs on a virgin machine will this cause any problems with speed? Will the runtime files care what codepage the exe was compiled under?

Sorry for the roundabout question.

 

[alvechurchdata]

I always compile the Config.Fpw into the executable so that Fox won't go looking for any rogue files. Just add it to the Text Files under the Other tab of the Project Manager.

Geoff Franklin

http://www.alvechurchdata.co.uk

 

[yert33]

Thank you. I will do.

I've just finished converting all my DBF's and PRG's to codepage 1252 and voila! it's fast again....

Thank you