Define files

In the column active of the Remote Transport configuration all fields that should be transported are marked with a doubleclick. Line 2 with the project basis path cannot be deactivated. The project files always are transported.

The source paths should always be defined as relative to the project basis path.

Attention

All settings defined here also have an influence, if the project is used in a network! Everything which is to be transported here, will be transported to the clients during runtime resp. will not be transported.

Example

Transporting graphics is deactivated, because the graphics are on the server already. Then a client is started. The client finds out, that the graphics should not be transported and thus does not transport them to itself. So no graphics will be displayed on the client. Of course it also can be the other way round, so that files are transported to the client, that should not be transported.

As a default the project basis path, the graphics path, the list path, the video path and the report path can always be transported. From the project basis path the project.ini, the project.vba, the monitor.mon files and the directory 'project' are transported as a default.

All files in these directories will be transported.

Special case global project: If there is a global project in the workspace, it will automatically be listed for the transport in line 1. No additional settings have to be entered. Always all files necessary for the global project will be transported.

If additional files should be transported, these files can be copied to one of the standard paths or be entered additionally.

A click on the field Source with the right mouse button opens a context menu, where File selection or Directory selection can be chosen. Now single files or entire directories can be selected for the transport.

Then the column active of that line has to be activated, and now any files stated here will be transported with the project.

Attention

relative paths/files:

Here again alternative files can be entered reelative to the project basis path. This has the advantage, that independent of the target system the right directory structure always is retained.
Example: Under source you enter \\default.iso by hand. The Remote Transport now automatically knows, that the file is in the project basis path. The same procedure is possible for directories.

Usually only the target path of the project basis path has to be defined. The according path available on the target system has to be entered under Destination. Destination also may stay empty. The the files are transported in the same directory structure as defined under Source.

Info

relative paths/files:

If the source files are defined relatively, nothing has to be entered under Destination. (Only the destination of the project basis path). All other files then are automatically transported relative to this directory!
Example: If the file default.iso should be transported from the project basis path to the target system, you enter /default.iso under Source. The destination stays empty. The file then will be in the right place on the target system, namely in the project basis path.

Special case Windows CE: If the target system is a Windows CE terminal and no explicit destination is entered for the project basis path, the destination \Storage Card\Data is used as a default.

In newly added lines the entry of the column Revision defines, how to proceed with the according files during Remote Transport. Three possibilities are available here:

`Copy`	The file is copied to the remote system.
`Copy & register`	The file is copied to the remote system and entered in the registry.
`Copy & execute`	The file is copied to the remote system and executed there.