This document contains a lot of useful information about this and previous releases of ESL. We have also included a copy of the software licence for your information.
This file contains additional information not covered in the standard documentation and important information you need to know before using ESL.
Please take the time to familiarise yourself with
Please refer to this information before contacting us.
Versions of Windows
ESL 18.20 has been tested with the following versions of Windows;
•Windows Server 2012 (64bit)
•Windows Server 2016 (64bit)
•Windows 7 SP1 (64bit)
•Windows 7 SP1 (32bit)
•Windows 10 (32bit)
•Windows 10 (64bit)
We have suspended testing Windows 8 as we are unaware of any of our customers using this platform. If you wish to use Windows 8 or any other versions of Windows not listed, please contact the ESL Helpdesk.
Versions of Visual Studio
As Microsoft have dropped support for Visual Studio 6 (VS6), since version 13.10 we have introduced a version of ESL built using Visual Studio 2010 (VS10) and we will supply this build version. If your ESL Application uses any customer written dynamic link libraries (.dlls) that access an ESL function contained in ESLLIB, then these libraries must be re-linked to ensure the correct calling conventions are used.
If you have any specific questions regarding the differences, please do not hesitate to contact us.
As of version 14.20, the calling convention used to call external routines has been changed. External subroutine must use the 'C' convention, i.e. calling routine clears the stack. External functions must use the standard convention, as used by System APIs, when the called routine clears the stack. The macros ESLSUBAPI and ESLFNCAPI contained within the supplied source code header EslLib.h, can be used to ensure the correct convention is used. Depending how the entry points have been defined, you may find that the "Linker" decorates the function name with an "@" symbol suffix followed by the number of bytes pushed onto the stack. To remove this decoration, we recommend the use of an "Module Definition File", which explicitly names each entry point that can be called by your ESL application.
ESL provides access to any database, that has a 32bit ODBC driver, via the ESL Database Services library and the ESLODBC local application. When using a 64bit platform, you must ensure the 32bit version of the ODBC driver is installed, as ESL cannot access the 64bit API's, even though all data sources will be listed regardless of the driver's type. Microsoft recommends that when naming Data Sources, the driver type (i.e. 32bit or 64bit) is included in the name, as there is no facilities to determine whether a specified data source will be accessible. Due to the 32bit EHLLAPI standard used to perform "screen scraping", it is not possible to provide a 64bit version of ESL.
As of version 17.10, we have removed the old style bitmap fonts, contained within ESLFONTS font files and replaced them with True Type fonts contained within two files, "EslMono.ttf" and "EslCaps.ttf".
Whilst your applications can still use the old fonts, which date back to 1990, we recommend you improve the quality of the screen presentation by defining fonts, using the "font is" statement, based on the facenames "Esl Mono" and/or "Esl Caps".
Please see Fonts for more details.