Files of a new use

Batch\

InitFS.cmd

Init<FS>.cmd is called with the first activation of the application. The file is not changed after the production any more and can be adapted by the user. Normally the following actions are anchored in this file:

Application in the Pulldownmenü professional bowls anhaken.

Plan management open.

Signature table for announcement and printer load. All up to now loaded tables are removed.

Store of the symbolic table for this use. All up to now loaded symbolic tables are removed.

Icons available make.

Data bank for local information of the use tie together. The name of the data bank is identical with that of the use. The data bank is connected if possibly with writing rights.

Batch\

reInitFS.cmd

Reinit<FS>.cmd is called with the repeated activation of the application. The file is not changed after the production any more and can be adapted by the user. Normally the following actions are anchored in this file:

Application in the Pulldownmenü professional bowls anhaken.

Plan management open.

Signature table for announcement and printer load. All up to now loaded tables are removed.

Store of the symbolic table for this use. All up to now loaded symbolic tables are removed.

Icons available make.

Data bank for local information of the use tie together. The name of the data bank is identical with that of the use. The data bank is connected if possibly with writing rights.

Batch\

stopFS.cmd

stop<FS>.cmd is called by the call of another application and finishes the application. The file is not changed after the production any more and can be adapted by the user. Normally the following actions are anchored in this file:

Hooks in the Pulldownmenü uses take away.

Plan management close.

Data bank for local information of the use separate.

Batch\

userinit.cmd

userinit.cmd the information deposits in the system which application is active. The file is not changed after the production any more and can be adapted by the user. In this file deposited orders are explained by every Moskito's start.

Batch\Once\modellFS.cmd

Automatically generated Batchdatei with the commands to load of the model. The file is not changed on putting on the application any more. If necessary the command must be adapted to the store of the models by hand.

Batch\Once\InitFS.cmd

Automatically generated Batchdatei with the Registrierinformationen of the application. This puts down the name of the application on the list of the uses. After the production of the application this file is not changed by the system any more.

Batch\Once\

settingsFS.cmd

In this file all settings of the application are administered. The file is automatically generated and headlined with the securing of the application. All global variables (INI) with the prefix of the application are put down.

Database\ModellFS.mdb

While putting on an application an empty data model with the name of the application is generated. It is automatically loaded.

Register\FS

If an empty file with the name of the application includes: FS.

No ending is suspended. If in a list tree several uses are included a file is put on for each of these applications.

Signatur\

FS.sig

With activation of a use a signature table is automatically loaded with the same name. An empty signature table is automatically put on. This table fixes colours, line kinds and filling the lines and surfaces and must be filled by the administrator / user.

Symbols\FS.sym

Place for one or several symbolic tables with which point-shaped objects and object parts are coined. Normally the symbolic table is loaded with the name of the application. Other ones can be put down in the file initFS.cmd. The file (en) must be filled by the administrator / user.