Excert of an email response to TopGunF25
Sure, I'll explain how I have the 500 user application Set up.
1. All workstations have foxpro or the runtime modules install on the local hard drive. (MIS troops have VFP installed, All users have the Runtime modules.)
2. All Applications are compact exe's so the VFP libraries and runtime are not built into the EXE. Makes it smaller for faster file transfer.
3. All application.exe files sit on the server, but are copied to the workstation hard drive and started there. To do this I use a loader program, it copies the application from the server to the local hard drive and then starts it. The application starts by calling a renamed config.fpw file that called the loader.
4. The Windows Desktop Icon parameters are:
(MIS troop example of Icon)
Target: "C:\Program Files\Microsoft Visual Studio\Vfp98\VFP6.EXE" -t -cF:\bidsys\bidsys.cfg
Start in: "f:\bidsys"
5. All file locations are stored in a database BIDSYS.DBF. At program startup the database is opened , the fields are placed in memvars, and all files are called using the memvars.
set code example below.
6. Each workstation does not do any work on a Server Hard drive. I have a copy of a FoxUser.dbf and FPT in the server main application directory but renamed to bidsyscf. I have the bidsyscf set to the way I want it. The main application copies the bidsyscf to the local hard drive and then sets the resource to that copy. As you may have noticed above, I have a FoxPro Config.fpw commands built into the loader file.
....
do SetFcmem && declares all F* Memory Variables
on error **
if !file(fcTempDir+"BIDSYSCF.FPT"
use (fcSysDir+"BIDSYSCF.DBF"
copy to (fcTempDir+"BIDSYSCF.DBF"
endif
set resource to (fcTempDir+"BIDSYSCF.DBF"
...
7. All temp files, Views, Text Files, Queries, etc are done on the local hard drive.
example
use (fcSysDbf + " CUSTPROJ"
select * from CUSTPROJ;
where CUSTPROJ.QUE_DATE = ldDate;
into table (fcTempDir + "CUSTPROJ.DBF"
or
create view (fcTempDir +"CUSTPROJ.VUE"
etc
8. In short, the file server just sits there with the files open. It does not do any work at all. No files are created on it, I even have the directory rights for file create turned off for users, Only MIS personnel have file creation rights on the server. All file create actions are performed on the local hard drive.
9. Ok here comes the start of the Old School. I have done tests on applications were all files are closed and only opened when needed and on systems where all files are opened at the beginning of the application and left open until the applications ends. I have found that if you only open dbf's as you need then, the system runs faster when the dbf's are on a local hard drive. It runs faster if all dbf's are opened at the start of the program when the dbf's on are on a server. I have formed a comprise. When the user is sitting at the Application Main Menu (not a sub menu) , all DBF's are closed except for the ones needed by the main menu for security/authorization reasons. Any program called from the main menu has Close Data as the first or second command line. Any files needed by the application are opened in the app and left open until the return to the final menu is made.
I Hope This Helps You David W. Grewe
Dave@internationalbid.com
ICQ VFP ActiveList #46145644
