The following table lists the error codes that may pop up when FileMaker detects something out of whack in your database, especially when you’re writing or running a script. You’ll run into error codes when you’re testing a script with the Script Debugger in FileMaker Pro Advanced or if you use a
Get(LastError) calculation. Like many things written by and for computer programmers, these descriptions may not make much sense in English, but they may provide a little more guidance than the error number alone.
Error codes marked with an asterisk (*) apply only to web-published databases.
Command is unavailable (for example, wrong operating system, wrong mode, and so on)
Command is unknown
Command is invalid (for example, a Set Field script step does not have a calculation specified)
File is read-only
Running out of memory
Requested data is missing
Name is not valid
Name already exists
File or object is in use
Out of range
Can’t divide by zero
Operation failed, request retry (for example, a user query)
Attempt to convert foreign character set to UTF-16 failed
Client must provide account information to proceed
String contains characters other than A-Z, a-z, 0-9 (ASCII)
Command/operation canceled by triggered script
Map Win32 error of “ERROR_NOT_Supported.” Microsoft documentation is “the request is not supported.”
The file ...