Mac OS X
Components Crossplatform Mac & Win Server Client Old Guides Examples
New in version: 7.5 8.0 8.1 8.2 8.3 8.4 8.5 9.0 9.1 9.2 Statistic
Initializes the XL library by loading it.
|Component||Version||macOS||Windows||Server||FileMaker Cloud||FileMaker iOS SDK|
|LibPath||Native path to the DLL on Windows or Dylib file on Mac OS X.||"C:\libxl\libxl.dll"|
|LicenseName||The name of your libXL license.||""|
|LicenseKey||The license key of your libXL license.||""|
Returns OK on success.
DescriptionInitializes the XL library by loading it.
You can keep the library in a database field and export it at runtime to a known location and load it from there.
If you have no license yet, you can test this function by passing empty strings for name and key.
For getting a license key, please visit the libXL website:
Starting with version 4.4, you can pass just the filename of library and the plugin finds it in the Extensions folder or in FileMaker's application folder.
Windows error 193 means that 64-bit FileMaker tried to load 32-bit library or 32-bit FileMaker tried to load 64-bit library. The bit level must match between app and library. For Mac OS X the error message will tell you about wrong architecture.
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.
Initialize when needed:
Initialize with license key on Windows with Server:
- XL/Export records
- XL/Sheet with colored text
- XL/Writing data
- XL/Edit Sheet
Created 18th August 2014, last changed 5th April 2019
Feedback: Report problem or ask question.
MBS FileMaker Plugins