Could not open OLE object a5contexteval.contexteval
/pages/Desktop/Reference/Design/OLE/Could not open OLE object a5contexteval.contexteval.xml
Error running "startup_xdialog_context" could not open OLE object 'a5contexteval.contexteval.
<> Not Equal To
/pages/Ref/Xbasic/Operators/Comparison Operators/Not Equal To.xml
The result is TRUE if the expressions on both sides of the operator are not equal, i.e. if both Operand1 and Operand2 are of different types or have different values.
Variables to NOT persist
/pages/Guides/Mobile and Web Components/UX/Properties/Local Storage/Variables to not persist.xml

One or more variables that should not be persisted to Local Storage. This property is only available when *[ui:Persist variable values]* is checked.

!= (Not Exactly Matching Operator)
/pages/Ref/Xbasic/Operators/Comparison Operators/Not Exactly Matching Operator.xml
The Not Exactly Matching operator returns .T. (TRUE) if the expressions on both sides of the operator both, Operand1 and Operand2, are of different types or have different values.
High Order Characters Not Printing Correctly
/pages/Troubleshooting/Reports/High Order Characters Not Printing Correctly.xml
UTF8 Support was added to Reporting Alpha Anywhere, before UTF8 was supported, reports used localization 'Active Code Page'. When a report is printed with 'allow all international characters in a free-form report' Option set to true, all fields return UTF8 encoded content, while the legacy setting of 'false' causes fields to return ACP encoded data. In the case of data that is originally UTF8 encoded, using ACP can cause loss of characters not included in the 'Active Code Page'.
SQL Server - Function request not Supported
/pages/Troubleshooting/Databases/SQL Server Function request not supported.xml
The "Function request not supported" error is a SQL Server error that occurs when doing a SQL query that includes date fields and a SQL Server. This error is usually caused because the wrong SQL Server drivers are installed on the system.
Debug an Image File Reference Image Not Displaying Correctly
/pages/Troubleshooting/Debugging/Debug Image File Reference Images Not Displaying Correctly.xml
If you have built a Grid that contains Image File Reference fields, and the images are not displaying when you run the Grid, this topic can help you find the problem.
Error Style Not Recommended - Warning Message
/pages/Troubleshooting/Components/error style not recommended for containerwidth layout.xml
A UX Component configured to use the 'ContainerWidth' Layout type and using either an 'icon' or 'inline' Error style may issue a warning message when the component is saved.
The ordinal 2630 could not be located in the dynamic link library LIBEAY32.dll
/pages/Troubleshooting/Web Server/The ordinal 2630 could not be located in the dynamic link library LIBEAY32.dll.xml
This error message can occur when an older version of OpenSSL is running on your computer when Alpha Anywhere is installed. It is only a real problem if Alpha Anywhere will not start after installation. See the Installation issues section of Encryption Algorithms for more information.
Using Tables and Sets That are Not Part of a Workspace
/pages/Guides/Desktop/Design/View/Database/Using Tables and Sets That are Not Part of a Database.xml
There is actually no need to have all of the tables and sets in an application be members of the workspace. Iin fact, you could build an application where none of the tables and sets are in the workspace. If you do this, the change that you would have to make in your Xbasic would be to full qualify references to forms, reports, tables, etc.