Topics   All   Mac OS X (Only)   Windows (Only)   Linux (Only, Not)   iOS (Only, Not)  
Components   Crossplatform Mac & Win   Server (Not)   Client   Old   Guides   Examples
New in version: 6.4   6.5   7.0   7.1   7.2   7.3   7.4   7.5   8.0   8.1    Statistic  


Creates output file for writing debug messages.

Component Version macOS Windows Server FileMaker Cloud FileMaker iOS SDK
CURL 2.6 Yes Yes Yes Yes Yes

MBS( "CURL.CreateDebugOutputFile"; Handle; Path )


Parameter Description Example value
Handle The CURL session handle. $curl
Path Native file path. C:\Documents\Test.Txt


Returns "OK" on success or error message.


Creates output file for writing debug messages.
Debug messages are written to file if you use this functions and debug messages are always collected for calling CURL.GetDebugAsText after the transfer. This can be useful as you can have your FileMaker solution write a copy of debug messages in temporary file. If your client has problems, you can simply read messages from last transfer. If creation of the file fails, you get an error message back, but still your transfer will probably succeed.
Do not call this method while a transfer is running.

Logging to a file is useful to read messages in case FileMaker crashes while a transfer.

This function requires a native path. Use Path.FileMakerPathToNativePath to convert a FileMaker path to a native path if required. If you like to have the user choose the path, you can use FileDialog functions.
For Server be aware that server has limited permissions and may not be able to access all files on a computer.


Write copy of debug messages to a file into temp folder on Mac:

MBS( "CURL.CreateDebugOutputFile"; $curl; "/tmp/LastMessages.txt" )

See also

Example Databases

CURL.CloseOutputFile   -   CURL.CreateHeaderOutputFile

Feedback: Report problem or ask question.

MBS Xojo tutorial videos