When a file name must be entered, in data import/export operations for instance, it must be defined in the usual way, according to the operating system. Examples of file paths:

  • /u/temp/myfile.asc
  • E:\tmp\myfile.txt
  • \\server\path\myfile.tst

Unless a network path is given (this path should be accessible from the application server), these paths define locations that are on the application server.

A path can be relative. In that case, it refers to a directory that is linked by default to the operation using the file. This is normally a directory that is located in the base directory of the folder.

If the user wants to access a directory located on a server on which an Adonix service functions, the following syntaxes are to be used:

  • server@path
    •
  • server:service@path

where: server is the network name of the server, service is the service number (if this information is omitted, the current service number is used), and path is the path itself on the server.

There is a particular case: if the user wants to write on the client workstation. In that case, the syntax is:

  • #@path

Note that this syntax functions very well in client-server mode, but it causes security and authorization issues in Web mode. In version 140, it is not possible to circumvent these security problems. In version 150, it is possible to load, on the Web workstations that need it, a simplified engine that will perform the file loading operations in both directions (upload/download).