Components Crossplatform Mac & Win Server Client Old Deprecated Guides Examples Videos
New in version: 9.4 9.5 10.0 10.1 10.2 10.3 10.4 10.5 11.0 11.1 Statistic FMM Blog
Creates output file for writing debug messages.
|Component||Version||macOS||Windows||Linux||Server||FileMaker iOS SDK|
|CURL||2.6||✅ Yes||✅ Yes||✅ Yes||✅ Yes||✅ Yes|
|curl||The CURL session handle.||$curl|
|Path||Native file path.||C:\Documents\Test.Txt|
Returns "OK" on success or error message.
DescriptionCreates 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:
- Version 11.1
- Added extra line to CURL debug log to indicate the version of MBS Plugin, CURL library used and what OS is used and FileMaker application. See CURL.CreateDebugOutputFile and CURL.GetDebugAsText functions.
Created 18th August 2014, last changed 15th June 2016
Feedback: Report problem or ask question.
MBS Xojo Chart Plugins