...
Description:
| Code Block | ||||
|---|---|---|---|---|
| ||||
FUNCTION xpfMapFile (fileName : STRING;
mode : INTEGER)
mappedFileName : STRING;
|
The function xpfMapFile maps the given file name to the EDM_SERVER_CLIENTS_FILES_PATH. Note:
| Info |
|---|
When using server side files, there are no concurrency control or synchronization of such files. Nor are such files controlled by transactions, i.e., no rollback in aborted transactions. All such control must be performed by the actual (xpx) application itself. |
...
Server side files are files located in the EDMserver's directory defined by the EDM configuration variable EDM_SERVER_CLIENTS_FILES_PATH . Can be combined with xpxSetUtf8EncodedFileNames |
...
Argument type
...
Argument name
...
Comments
...
STRING
...
fileName
...
|
Arguments
...
| Type | Name | Comment | |
| STRING | fileName | comments | |
| INTEGER | mode |
Return
...
Value
...
| Type | Argument nameName | CommentsComment |
| STRING | mappedFileName | %EDM_SERVER_CLIENTS_FILES_PATH%\fileName |
...
Options
...
| Option | Comment |
XPXINPUT | file used for input to the server |
XPXOUTPUT | file used for output from the server |
XPXINPUT_XPXOUTPUT | file used for input and output by the server |
Comment:
When using a xpf function the developer must use correct exception handling to catch any error that has occurred. Please see xpxThrow function for details.
EXAMPLE
Example
...
| Code Block | ||
|---|---|---|
| ||
<Missing Example> |
See also
| Filter by label (Content by label) | ||||||
|---|---|---|---|---|---|---|
|