While your system may have multiple same-version Clarions installed at different paths and/or on different drives, only ONE of any given Clarion version may be the currently-in-use clarion installation for that version.

This utility tracks where your various Clarion installations are installed and configures the correct registry settings any instance of a given Clarion version requires to run successfully.

To set to any Clarion version before running it, open this app and select "Clarion 9.1", "Clarion 10", "Clarion 11" or "Clarion 11.1" from the main window.

Then, from the pop-up menu choose "INFO" to determine where the currently active instance of that Clarion version is located.

If you have more than one installation of that Clarion version, you can configure the registry by choosing "SET" to that version's installation directory.

HNDENCRYPT.EXE source code, because it is in Clarion .APP format, is included as a standard part of the CHT toolkit, provided both in .APP format as well as ready-to-run, in .EXE format.

HNDENCRYPT.EXE command-line parameters are as follows:

** HELP **
--help [OPT]
    Pops up a splash help screen.
--silent [OPT]
    Suppresses log and help file popups.

** ENCRYPT/DECRYPT **
--input [REQ]
    Path and name of input file.
    If the path is omitted, the .EXE path is assumed.
--output [REQ]
    Output path only - local to this exe if omitted.
--mode [OPT]
    Encode or decode - defaults to encode if omitted.
--key [ALONE]
    Encrypting password stored.
--key ???
    Display stored password.

The output file name is formatted from the input file with a .hzy extension. For example: test.pdf becomes testpdf.hzy.

The encrypted file is both compressed and encrypted by the operation of this CHT Batch Bot application. This operation is performed in a single pass whether encoding or decoding.

HNDFTPNET.EXE source code, because it is in Clarion .APP format, is included as a standard part of the CHT toolkit, provided both in .APP format as well as ready-to-run, in .EXE format.

HNDFTPNET.EXE is dependent on a CHT DLL called HNDNETFTP.DLL being present and visible on the system path, for its FTP capabilities.

The application communicates to this DLL via COM, requiring the HNDFTPNET.DLL to be registered on the host system. This DLL will auto-register on the host system when first called and found not to be registered.

CONFIGURING:
--config0
    [CFG] Set up FTP configuration information #0
--config1
    [CFG] Set up FTP configuration information #1
--config2
    [CFG] Set up FTP configuration information #2
--set0
    [CFG] Select and use configuration #0
--set1
    [CFG] Select and use configuration #1
--set2
    [CFG] Select and use configuration #2

COMMANDS:
--send
    [OPT] Provides file name of the local file to be uploaded.
    This file need not exist if used with the --mask tag to
    to indicate that a pre-zip is performed using a mask.

--remote
    [REQ] Names the remote directory with which to interact.
    This is a required parameter which is formed as follows:
    /ftprootdir/subdir1/subdir2/

--local
    [OPT] Names a local directory when the --mask tag
    is used to describe one or more files for pre-zipping.
    Defaults to the application directory if omitted.

--pwd
    [OPT] Password used when pre-zipping with --mask.

--mask
    [OPT] DOS-style file mask (eg: *.app) describes files to be
    zipped. Requires CHTSNAPZIP.EXE to be available.
    --send parameter must be .zip file name

--fetch
    [OPT] File name of a remote file to be downloaded.
    Use instead of --send or --erase when downloading.

--erase
    [OPT] Provides file to be erased from a remote directory.
    Use instead of --fetch and --send when deleting.

--list
    [OPT] Used by itself, this provides a file listing
    of the remote directory stipulated after the tag.
    E.G. --list /web/subdir/

LOGGING:
All successful transactions or errors are logged into "hndftpnet.log" located in the same directory as the hndftpnet.exe.

HELP:
--help
    [OPT] Used by itself, this pops up a splash help screen
    Creates hndftpnethelp.txt which contains the contents of
    this splash screen.

The email template used to build this application is EMBED CDO MAIL FUNCTIONS. The CHT CDO Class is called HNDMSCDO located in files HNDMSCDO.INC and HNDMSCDO.CLW.

HNDMAILCDO.APP source code, because it is in Clarion .APP format, is included as a standard part of the CHT toolkit, provided both in .APP format as well as ready-to-run, in .EXE format.

HNDMAILCDO.EXE runs from the DOS prompt or can be called from another application using Clarion RUN or CHT's HNDSNAPCALL class. It accepts several command line parameters that describe the email to be sent. These parameters are as follows:

SENDING:
--to
    [REQ] mymail@address.com;mail@address.com;
--cc
    [OPT] mymail@address.com;mail@address.com;
--subj
    [REQ] This is the subject line.
--file
    [OPT] emailbody.txt/.html (contains body text)
--attach
    [OPT] somezip.zip (Attachment requires full path)

CONFIGURING:
--config0
    [CFG] Set up mail configuration information #0
--config1
    [CFG] Set up mail configuration information #1
--config2
    [CFG] Set up mail configuration information #2
--set0
    [CFG] Select and use configuration #0
--set1
    [CFG] Select and use configuration #1
--set2
    [CFG] Select and use configuration #2

LOGGING:
All transactions such as config changes, emails or errors are logged into "hndmailcdo.log" located in the same directory as the hndmailcdo.exe.

HELP:
--help Pops up a splash help screen and help file hndmailcdohelp.txt
--silent [OPT] Suppresses popup logs and help during mult-recipient sends

The CHT template illustrated in this application is called SOURCE_ EMBED_ MAPI_ FUNCTIONS. The class underlying this template is called HNDIMAIL located in files HNDIMAIL.INC and HNDIMAIL.CLW.

HNDMAILMAPI.APP source code, because it is in Clarion .APP format, is included as a standard part of the CHT toolkit, provided both in .APP format as well as ready-to-run, in .EXE format.

When you have a properly configured MAPI email client like Outlook or Windows Live Mail configured, this application is able to connect with it to send email. This application is stand-alone and requires no other CHT Dlls.

HNDMAILMAPI.EXE runs from the DOS prompt or can be called from another application using Clarion RUN, or CHT's HNDSnapCall Class, from a batch file or even from a .VBS script. It is capable of sending standard email of the type(s) configured in your default email client.

It accepts several command line parameters that describe the email to be sent. These parameters are as follows:

SENDING:
--to    
    [REQ] mail@address.com (or multiples + semi-colons)
--cc
    [OPT] mail@address.com (or multiples + semi-colons)
--subj    
    [REQ] This is the subject line.
--file    
    [REQ] emailbody.txt (Contains body text)
--attach
    [OPT] somezip.zip (Name of attachment requires full path)

LOGGING:
All transactions such as config changes, emails or errors are logged into "hndmailmapi.log" located in the same directory as the hndmailmapi.exe.

HELP:
--help Pops up a help text file hndmailmapihelp.txt
--silent Suppresses popup-help during multiple sends

Before you use it, the application must be configured with valid email parameters the same as any other smtp email client requires configuration. This application is stand-alone but requires the DLL mentioned above be located on the target machine and registered via REGASM.EXE.

HNDMAILNET.APP source code, because it is in Clarion .APP format, is included as a standard part of the CHT toolkit, provided both in .APP format as well as ready-to-run, in .EXE format.

The CHT email template used in this application is EMBEDNETSMTPCLASSES. The CHT class underlying this template is HNDNETSMTPCLASS located in files HNDNETSMTP.INC and HNDNETSMTP.CLW.

HNDMAILNET.EXE runs from the DOS prompt or can be called from another application using Clarion RUN, or CHT''s HNDSNAPCALL class, or run from a batch file or even from a .VBS script. It is capable of sending standard SMTP email as well as SSL SMTP email as found with GMAIL, HOTMAIL and other similar services.

It accepts several command line parameters that describe the email to be sent. These parameters are as follows:

** SENDING:
--to
    [REQ] mail@address.com
--cc
    [OPT] mail@address.com
--bcc
    [OPT] mail@address.com
--subj
    [REQ] This is the subject line.
--file
    [REQ] smtpbody.txt (Contains email body)
--attach
    [OPT] somezip.zip (Requires full path to file)

CONFIGURING:
--config0
    [CFG] Set up mail configuration information #0
--config1
    [CFG] Set up mail configuration information #1
--config2
    [CFG] Set up mail configuration information #2
--set0
    [CFG] Select and use configuration #0
--set1
    [CFG] Select and use configuration #1
--set2
    [CFG] Select and use configuration #2

LOGGING:
All transactions such as config changes, emails or errors are logged into "hndmailnet.log" located in the same directory as the hndmailnet.exe.

HELP:
--help [OPT] Pops up a help document
--silent [OPT] Suppress pop up log and help file during mult-recipient sends.

HNDMAILSMTP.EXE requires correct configuration of a valid SMTP email setup with UserName, Password, Email Server and Email Return Address. Our template and SMTP classes provide a configuration function with user-controllable registry location setttings.

HNDMAILSMTP.APP source code, because it is in Clarion .APP format, is included as a standard part of the CHT toolkit, provided both in .APP format as well as ready-to-run, in .EXE format.

The email template illustrated is EMBEDSMTPFUNCTIONS. The CHT class underlying this template is HNDSMTP located in files HNDSMTP.INC and HNDSMTP.CLW.

HNDMAILSMTP.EXE runs from the DOS prompt or can be called from another application using Clarion RUN. It accepts several command line parameters that describe the email to be sent. These parameters are as follows:

SENDING:
--to    
    [REQ] mail@address.com;mail@address2.com;
--cc    
    [OPT] mailcc@address.com;mailcc@address2.com;
--bcc    
    [OPT] mailbcc@address.com;mailbcc@address2.com;
--subj    
    [REQ] This is the subject line.
--file    
    [REQ] emailbody.txt (Contains email body)
--attach    
    [OPT] somezip.zip (Name of attachment requires full path)

CONFIGURING:
--config0    
    [CFG] Set up mail configuration information #0
--config1    
    [CFG] Set up mail configuration information #1
--config2    
    [CFG] Set up mail configuration information #2
--set0
    [CFG] Select and use configuration #0
--set1
    [CFG] Select and use configuration #1
--set2
    [CFG] Select and use configuration #2

LOGGING:
All transactions such as config changes, emails or errors are logged into "hndmailsmtp.log" located in the same directory as the hndmailsmtp.exe.

HELP:
--help    
    [OPT] Pops up a help splash screen
--silent
    [OPT] Suppresses log and help file popups

HNDMAKEHZO.EXE builds compressed/encrypted file containers based on Clarion .TPS files. These file containers (.HZO extension) may be used like zip files, except they are relational, making them easy to browse, add to, or extract from in a non-sequential access fashion.

HNDMAKEHZO.EXE source code, because it is in Clarion .APP format, is included as a standard part of the CHT toolkit, provided both in .APP format as well as ready-to-run, in .EXE format.

HNDMAKEHZO.EXE command-line parameters are as follows:

--help [ALONE]
Pops up this splash help screen
--silent [OPT]
Supresses display of hndmakehzohelp.txt file

** Build A Container **
--input [REQ]
Path of input directory
--output [REQ]
Path and name of output .HZO file

** Extract a Container **
--extract [REQ]
Name of container to extract
--target [REQ]
Name of target extraction directory

** Used wth Build or Extract **
--pass [OPT]
Encrypting/decrypting string of characters representing password.
--query [OPT]
CHT Query to describe files for input or output

The application accepts several command line parameters that describe search values, replace values and more. These parameters are as follows:

--help
    [OPT] Pops up application splash screen.
    When used, all other parameters are ignored.
--mask
    [REQ] Required parameter eg: c:\temp\*.app
    Describes single or multiple files to be searched.
    Path required, unless file(s) in same directory as this exe.
--search
    [REQ] Required search text parameter.
    This describes what you're searching for.
--replace
    [OPT] Optional parameter if only a search
    This replaces the value under --search
--silent
    [OPT] Do not display log file after processing.

HNDSLFCMD.EXE can be called from one of your Clarion applications, from a Windows batch file or from a Windows .VBS script to provide reliable file upload, download and delete services.

HNDSLFCMD.EXE source code, because it is in Clarion .APP format, is included as a standard part of the CHT toolkit, provided both in .APP format as well as ready-to-run, in .EXE format.

CONFIGURATION COMMANDS:
--config0 to --config9
[CFG] Set up HTTP/HTTPS configuration information #0 to #9

SET COMMANDS:
"Set" commands may be combined with --send, --fetch or --erase.

--set0 to --set9
[CFG] Select and use configuration #0 to #9
--set
[CFG] Manually inserted url and port,
ignore config settings.
E.G. --set https://www.yoursite.org:88/
--userpass
[CFG] Manually inserted user and password
E.G. --userpass username:userpass

ACTION COMMANDS
--send
[REQ] Provides file name of the local file to be uploaded.
Use with --local to name the local pickup directory.
Use with --remote to name the remote target directory.
Multiple files may be listed, separated by commas.

--fetch
[OPT] File name of a remote file to be downloaded.
Use instead of --send or --erase for downloading files.
Use with --local to name the local target directory.
Use with --remote to name the remote pickup directory.
Multipe files may be listed, separated by commas.

--erase
[OPT] Provides file to be erased from a remote server.
Use instead of --fetch and --send when deleting.
Use with --remote to name the remote directory.
File names are separated by commas.

SOURCE/TARGET COMMANDS:
--remote
OPT] Remote directory with which to interact.
Remote directory below server /root/ directory.
Example usage: subdir1/subdir2/
Defaults to the server /root/ directory if omitted.

--local
[OPT] Names a local directory to indicate --send
pickup directory or to indicate --fetch target path.
Defaults to the application path if omitted.

HELP COMMANDS:
--help
[OPT] Pops up a splash help screen.
Creates .TXT file showing these instructions.

LOGGING:
All successful transactions and/or errors are logged into "hndslfcmd.log" located in the same directory as the hndslfcmd.exe.

HNDZIPNET.EXE source code, because it is in Clarion .APP format, is included as a standard part of the CHT toolkit, provided both in .APP format as well as ready-to-run, in .EXE format.

HNDZIPNET.EXE is dependent on one CHT DLL being present and visible on the system path, namely: HNDNETZIPPER.DLL.

The application communicates to this DLL via COM requiring the HNDNETZIPPER.DLL to be registered on the host system. The DLL will auto-register on the host system when first called and found not to be registered. Auto-registration can only be performed from an "admin" account.

** ZIPPING/UNZIPPING/LISTING ***
--zip
    Provides file name of the target ZIP file to be created.
    Note that the ESC key cancels ZIP operations in all cases.
    Use --path to name the source files location.

--unzip
    File name of the source ZIP file to be processed.
    Use --path to name the UNZIP location.

--list [ALONE]
    Lists the entire contents of the ZIP to "hndzipnet.log"
    and displays it in CHT Snap Edit.
    All other tags are ignored when --list is invoked.

--path [OPT]
    Names the root where --ZIP picks up files for processing.
    Names the root where --unzip places its files.
    The Start-In path is used when this tag is omitted.

--subs [OPT]
    Flags "true" that root path subdirectories be processed too.
    Flags "true" that the ZIP must incorporate paths.

--win [OPT]
    Flags "true" to indicate show a progress window.

--mask [OPT]
    Standard dos-style file mask to describe files to be
    zipped,, for example *.app

--qry [OPT]
    CHT-Style file query to describe files to be zipped.
    For example: NAME ENDSWITH APP OR NAME * .DCT

--silent [OPT]
    Flags do not pop up a results log on completion of the operation.

HELP:
--help [ALONE]
    Pops up this splash help screen.
    Creates a help file called "hndzipnethelp.txt"
    Displays "hndzipnethelp.txt" in CHT Snap Editor window.

LOGGING:
All successful oprerations or errors are logged into "hndzipnet.log" located in the same directory as the hndzipnet.exe.

ExplorerBrowse itself can also be extended by adding a variety of extension templates. This application adds PopFavoriteQueries_EXPB to provide a way to inject prebuilt queries into the browse to limit the records being displayed.

PopFavoriteQueries_EXPB provides a query control, a clear button, a favorites query selection control, a query builder button, a query save button and a query delete button.

The application also illustrates a procedure built with a CHT Jumpstart that allows you to manage and modify or insert pre-built queries.

It illustrates these concepts:
*** An Explorerbrowse implementation running
on SQL Data Tables.
*** CHT Query template PopFavoriteQueries_EXPB
*** Default query applied on browse opening
is under user, run-time control
*** Concatentaion of two fields (TELEPHONE + FAX)
in a single column
*** TELEPHONE and FAX are individually queryable
from PFQ_EXPB
*** SetExplorerBrowseQueryBindings - enables
querying of fields not individually displayed
in the browse. for example: FAX

This demonstration application requires the sample data tables provided with MICROSOFT ACCESS, called Northwind. The CHT toolkit installs these Northwind tables for you. The application finds these tables and registers them with ODBC if not already registered when you first run this demo app.

HMB itself can also be extended by adding a variety of extension templates. This application adds PopFavoriteQueries_HMB to provide a way to inject prebuilt queries into the browse to limit the records being displayed.

PopFavoriteQueries_HMB provides a query control, a clear button, a favorites query selection control, a query builder button, a query save button and a query delete button.

Its purpose is to study the use of the SQLite driver with CHT browses, and query templates set to UseSQL=True. We chose to "CHT-ify" this application specifically because it uses several SQLite data tables located in a repository file called SCHOOL.SQLITE.

A second purpose is, of course, to provide some visual and functional contast between a raw, wizard-produced, really UGLY and semi-functional, ABC application and ABC applications extended, enhanced and functionalized by a variety of CHT templates.

To analyse the allocation of templates in this application, open the application in the Clarion IDE and navigate to Global Extensions, select AACHTControlPanel and click on the menu item "Templates By Proc". This sequence of actions triggers an HTML document to display which enumerates and names all templates used in the application by procedure.

We chose to apply, as always, our "minimalist" screen design which avoids unnecessary use of tab controls, and shuns MDI child windows. Control buttons are for the most part kept to the toolbar and when placed on a window are always above the edit fields or list box.

This application applies, for the most part, CHT's browse extension template HandyMarkerBrowse (HMB); hence comes the name of the application. However, one procedure utilizes ListBoxBrowseExtender (LBX) which illustrates that an underlying ABC browse is no longer necessary to build fantastic Clarion browses. LBX browses are the bright future of data browsing with Clarion, ABC browses are the clunky past.

It illustrates these concepts:
* SQLFilter_HandyMarkerBrowse *
Includes a HandyMarkerBrowseQueryBuilderControl combined with a hand-built SQL query control using a standard entry control coded to post an SQL query to the data table.

* Hiding and unhiding columns programmatically
* SQL Query tracing on and off from a button click event
* SQL Query injection and browse reset to display results
* Use of HNDCUSTOM.TRN (Dutch) for translation
* Use of HNDPARSENEWDUTCH.TXT query keywords file

This demonstration application requires the sample data base provided with MICROSOFT ACCESS, called Northwind. The application will find the data base and register it with ODBC if not already registered.

* Hiding and unhiding columns programmatically
* SQL Query injection from a button click event
* SQL Query tracing on and off from a button click event
* Use of HNDCUSTOM.TRN (French) for translation
* Use of HNDPARSENEWFRENCH.TXT query keywords file

This demonstration application requires the sample data base provided with MICROSOFT ACCESS, called Northwind. The application will find the data base and register it with ODBC if not already registered.

It uses the SQLite driver, the ABC browse template, CHT's EXPB browse extension, set to UseSQL=True and CHT's QPFC query template.

To analyse the allocation of templates in this application, open the application in the Clarion IDE and navigate to Global Extensions, select AACHTControlPanel and click on the menu item "Templates By Proc". This sequence of actions triggers an HTML document to display which enumerates and names all templates used in the application by procedure.

We chose to apply, as always, our "minimalist" screen design which avoids unnecessary use of tab controls, and shuns MDI child windows. Control buttons are for the most part kept to the toolbar and when placed on a window are always above the edit fields or list box.

CHT TEMPLATES LEGEND:
EXPB = ExplorerBrowse
QPFC = QueryParsingFilterControl

That template is called ListBoxBrowseExtender or "LBX" for short.

Some Features Illustrated In This Application:
* ListBoxBrowseExtender Has Green Bar.
* LBX has multiple Query Control templates
* Use ORDER BY In Query For Mult-Column Sort.
* LBX Honours Retain-Record.
* LBX Generates Data Queue
* LBX connects update forms
* LBX has queue auto-fill on startup
* LBX has pre-filter to limit auto-fill on startup
* LBX has fill-queue methods for local or remote data

Six example procedures illustate some powerful LBX features;

* PROCEDURE:
LBX_1_ListBoxBrowseExtenderInQueueQuery()
This procedure illustrates a query template called InQueueQueryControl_LBX. This control filters the records already in the list box queue, into a secondary queue called "the shadow queue" and displays the result in the same browse. Clearing this filter resets to the starting or "Main" queue and displays the original record set. All of this except the original fill-queue happens without ANY further file access being needed.

* PROCEDURE:
LBX_2_ListBoxBrowseExtenderSortOrderFieldFilter()
This procedure illustrates a template called SortOrderFieldFilter_LBX. This control requires the user to enter only a string of characters to match something contained in the sort-order field. As above, matching data are inserted into the shadow queue and are displayed in the same browse. As above, also, clearing this filter resets to and displays the "Main" queue record set.

* PROCEDURE:
LBX_3_ListBoxBrowseExtenderUniversalQueryControl()
This procedure illustrates a template called UniversalQueryControl_LBX. This control when empty fills the queue with all table/view records unless a pre-filter is added to the template config. Click the "Queue Data" button to switch to the "Shadow Queue" and enter a query. These records are filtered from the Main queue into the Shadow queue. Click back on the "Queue Data" button and the browse switches back to the Main queue with all original records intact.

* PROCEDURE:
LBX_4_ListBoxBrowseExtenderPopFavoriteQueries()
This procedure populates a template called PopFavoriteQueries_LBX. This control opens a table called PreQueries and scans it for queries designated for the view name defined on the template. Queries may be optionally added, or deleted at run time and can be selected from a popup menu. The PreQueries table is defined in HNDO.DCT from which it can be imported into your own dictionary. Prequeries may be ISAM or SQL as required by your application.

* PROCEDURE:
LBX_5_ListBoxBrowseExtenderConditionalIconsOneColumn()
This procedure populates a template called UniversalQueryControl_LBX as above, but its purpose is primarily to illustrate conditional icons. These are icons on a column or columns which change based on some conditional expression related to the data in that column. In this case columns beginning with A, B, C and D are assigned icons 1, 2, 3, and 4. To see the effect of this, set the "Max Pre-Load" value to at least 1000 and click the NAME column to sort from smallest to largest.

* PROCEDURE:
LBX_6_ListBoxBrowseExtenderConditionalIconsTwoColumns()
This procedure populates a template called UniversalQueryControl_LBX as above, but its purpose is primarily to illustrate conditional icons. These are icons on a column or columns which change based on some conditional expression related to the data in that column. To see the effect, set the "Max Pre-Load" value to at least 1000 and click the SSN or NAME columns to sort from smallest to largest.

** AppBuildNumberStamp,
** AppCopyRightStamp
** AppBuildDateTimeStamp
** HandyAddressControls
** HandyCOMProgressBarControl
** HandyCOMSliderControl
** HandyThreadLimiter
** HandyToolBarGradient
** HandyWindowGradient
** VisitHandyControl
** HandyHelpFileFetch
** HandyMailMeControl_EWF
** HandyCOMMAPIControl
** HandyRulerControl
** HandySliderControl
** HandyTellMeControl
** VisitMeControl
** HandyHyperLink_EWF
** HandyWindowDismissButton
** HandyWindowsNotePadButton_EWF
** HandyCOMDigitalClockControl
** HandyHelpButtonControl
** HandyRegionButton
** HandyCOMAnimationControl
** HandyCOMDatePickerControl
** HandyDriveSelectorControl
** HandyFileSelectorControl
** HandyGradientEllipse
** HandyGradientRoundBox
** HandyHelpFileTopicButton
** HandyPopupCalendarButton
** This is a (TIER-4) application

ApplicationImagesEx keeps track of the images used in your application and controls consistency of your visual style in a format that can be saved for reuse and more.

EmbedWindowFunctions provides, advanced icon menus, application-in-tray, window boxes and more.

Procedures in this application are available as JUMP START procedures via the CHTJumpStartProceduresUtility Template under the topic Main And Splash.

You are able to identify the name of the Jump Start Procedure being illustrated and tested here from the MAIN MENU of the application.

We're making this application available to you as an alternative to using CHT JUMP START templates. Use our AAExportProcedure Utility Template to export a procedure from this application as a .TXA. Then, use our AAImportProcedure Utility Template to import the resulting .TXA to your own application.

You are able to identify the name of the Jump Start Procedure being illustrated and tested here from the MAIN MENU of the application.

We're making this application available to you as an alternative to using CHT JUMP START templates. Use our AAExportProcedure Utility Template to export a procedure from this application as a .TXA. Then, use our AAImportProcedure Utility Template to import the resulting .TXA to your own application.

Extension template EmbedCalculatorFunctions attaches a CHT class called HNDCalcControl to your application procedure, making its functions available to the procedure.

Control template HandyCalcEntryControl_ECF drops an entry control and a button on your procedure window. These controls work in tandem. A numerical value in the entry control is passed to the calculator - accessed via the button control - and the calculator passes a calculated result back into the control. A thread option on the tempate provides for passing data back to the entry control without closing the calculator, which can be left open on top of the application window.

HOW TO USE THIS UTILITY:
Configure an "HTML Source Directory" and a "PDF Target Directory". The HTML file pickup location is determined by the "Source" value and the PDF creation location is determined by the "Target" value.

Next, select the .HTM or .HTML file names that you want to convert to PDF documents. These file names are then stored in the HNDHTML2PDF.TPS file along with a complete path, and a TIME, DATE and SIZE stamp. Since the file names and dates are stored, the date-time-size stamp on these files remains static. However, a double click on any file name forces an refresh of the DATE, TIME, SIZE information provided for any file.

Using the multi-select feature of the CHT LBX browse on the conversion dialog window, highlight the file or files that should be processed into .PDF's.

Click the PDF button on the window toolbar to begin PDF creation. Files with the same names and a .PDF extension are created in the "PDF Target Directory".

TO USE THIS UTILITY:
First, select all the .TPL file names that you want to register from \templates\win\ and from \accessory\template\win\ into the application browse. These file names are stored in the HNDTPLREGISTRY.TPS file under the application directory. You only need to do this first step once, unless extra templates not already selected and stored are required.

Next, close the Clarion IDE version being addressed if it is running, as the application will refuse to register templates if it detects that Clarion version is still running.

Next, select the templates you wish registered using the CHT LBX browse record selection method. Browse record selection works as in any CHT HandyMarkerBrowse or CHT ListBoxBrowseExtender browse.

Finally, click the "Register" button on the toolbar. The application confirms with you, that the Clarion IDE being targeted is NOT running. Once confirmed, it renames the current \template\win\clarionregistryXX.trf and registers the templates selected in the application browse.

Note 1: ABCHAIN.TPL is automatically registered first, before any other selected templates. This is the master ABC template on which many other sets depend. If it is selected in the .TPL list, no harm done.

Note 2: This application creates a brand new clarion .TRF file with only the selected templates and ABCHAIN.TPL. In other words, a brand new .TRF is created, not a revised version of the existing one.

As usual, subscribers with a SOURCE code subscription receive the code module as well as the header. DLL version subscribers receive only the header module and the class code is in one of the CHT DLLs.

The application illustrates the syntax used to call many of the functions available in the HNDDates class. There are also two separate implementations of the calendar showing how you can modify the look of the CHT calendar by calling methods like OBJ.SetCalendarIcon() and embedding new calendar image properties in that method.

A CHT control template called HandyCOMCalendarControl helps you drop this control onto any application window and instantiate a Clarion-style interface to the OCX ICalendar control.

Source_EmbedMAPIFunctions template
Source_EmbedZipFunctions template

The MAPI template provides an embeddable CHT class called HNDIMAIL located in HNDIMAIL.INC and HNDIMAIL.CLW. Since this app uses the system's MAPI client email configuration, a working, configures MAPI client is required to be present.

The ZIP template provides an embeddable CHT Class called HNDComZipClass located in HNDZIPPR.INC and HNDZIPPR.CLW.

This COM class requires HNDZIPR.OCX be registered to COM on the system using REGSVR32.EXE. This app will do that automatically, but to test on another machine where CHT is not installed, this app's executable and the HNDZIPR.OCX should be placed together in the same directory.

If you want to learn to hand code with these two classes, this application is a perfect learning platform. The procedures provided may also be imported directly into your apps to provide pre-built functionality.

Source_EmbedSMTPFunctions template
Source_EmbedZipFunctions template

The SMTP template provides an embeddable CHT class called HNDSmtp located in HNDSMTP.INC and HNDSMTP.CLW.

The HNDSMTP class requires an SV DLL called CLARUNEXT.DLL which is available with SMTP capability only in Clarion Enterprise (the expensive one).

The ZIP template provides an embeddable CHT Class called HNDComZipClass located in HNDZIPPR.INC and HNDZIPPR.CLW.

This COM class requires HNDZIPR.OCX be registered to COM on the system using REGSVR32.EXE. This app will do that automatically, but to test on another machine where CHT is not installed, this app's executable and the HNDZIPR.OCX should be placed together in the same directory.

If you want to learn to hand code with these two classes, this application is a perfect learning platform. The procedures provided may also be imported directly into your apps to provide pre-built functionality.

** JumpStartBulkFileCompressExpandWithProgress()
  -Bulk file compression and expansion with encryption and decryption
** JumpStartBulkFileContainerizeWithProgress()
  -Bulk file compression to a container (.HZO) file with encryption.
** JumpStartBulkFileDeContainerizeWithProgress()
  -Bulk file decrompression from container (.HZO) file
** JumpStartBulkFileCopyWithProgress ()
  -Bulk file copying to a target directory
** JumpStartBulkFileEncryptDecryptWithProgress()
  -Bulk file encryption/decryption with mpression, decompression
** JumpStartBulkFileEraseWithProgress()
  -Bulk file removal
** JumpStartBulkFileMoveWithProgress()
  -Bulk file moving
** JumpStartBulkFileRenameWithProgress()
  -Bulk file renaming

** A query allows you to describe the files to be acted on. Or files to be acted on may be dropped from MS File Explorer.

BulkSearchReplaceText() -
Searches through text and program code files of all types in the target directory to replace words, commands, phrases.

BulkFileRename() -
Adds a prefix and removes spaces and extended characters from filenames in the target directory.

This text client will let you ask new questions and post new comments as you always have. The data tables attached to this forum started life in early 2022 and you are able to query back to then. Older data has been removed as many of the questions are no longer relevant to the latest CHT templates.

The data tables in use are TOPSPEED type which have a reputation of not being very speedy across a WAN using standard operating system network connections. That reputation for slowness exists because a typical one piece data application is separated from the data tables across the network.

Normal operating system streaming speeds, are severely limited across a WAN. And while SQL data streaming speeds are a bit better, they are still not up to the speeds that can be achieved using HTTPS across the WAN or the Internet.

You will, no doubt, discover when you browse this forum, that it is amazingly fast, as though the data tables were local to you. That's because CHT uses a two-piece application approach. The server is near the data tables where it needs to be, and that design localizes the amount of standard network streaming to mere inches, since the tables and server are on the same computer hardware.

The user interface, the client part that you are using here, is connected to the server by a far faster protocol over secure HTTPS using a highly encrypted and compressed data stream.

Try it and discover the speed for yourself!

This app is available as HNDCLIENTCL.EXE in your \accessory\bin\ directory. You can launch it from there. It is also provided as HNDCLIENTCL.APP in the \hndapps\ directory if you would like to examine and perhaps re-purpose it for your own use.

A TYPE 3 server, is based on secure, encrypted delivery to a set of customers or clients that sign in with individual passwords. The server maintains and authenticates against a server-side customer/client table. See HNDFILSV.DCT for and example customer table design.

This "Basic" version has had all non-essential componentry removed and focusses entirely on CHT templates and classes required to build a fast, efficient CHT secure file client using a 3-piece login.

This client application has a matching demonstration server called HNDFILSV.APP which is configured to provide secure upload and download services.

This client provides both compressed and encrypted file movement services without requiring either pre-compression or pre-encryption of the transported files.

Type 4 servers provide server-level authentication, rather than individual user-specific authentication. This type of server does not normally have a user data table associated with it though it could.

HNDSLFCL.APP illustrates how to make secure file upload and download requests to and from a CHT server root directory or any directory below server root.

A log-in dialog has been added, under an unlock image button on the tool bar. This produces an XSA, 2-part authentication dialog for server-level authentication prior to transfer access being allowed. The ACCOUNT ID and PASS CODE #, entered must match the same two values established on the server.

HNDSLFCL.APP illustrates two secure file transfer functions: HTTPGetFileSecure() and HTTPPutFileSecure() which provide a progress window with a cancel button.

These two functions are hosted in CHT Class HNDCLIENT and are made available in the application by a template called EmbedHTTPClientFunctions.

Several demo client applications are provided to CHT subscribers: HNDFILCL.APP and HNDINSTALLMYFILES.APP. Another client application called HNDHTGT.APP illustrates making on-the-fly file requests from this server using the HNDHTTP and HNDHTTPClient classes.

The server maintains complete control of which files and directories are visible to the client. File transfers are optionally compressed and/or encrypted at the request of the client application.

This is an "Authenticating" server. The client logs in by providing "LastName", "LoginID" and "EmailAddress". The server, unless reconfigured uses a member file called HNDFILSVMEM.TPS. New members may be added as required to customize the users list.

NOTE: This is a starting-point server from which to build forward. The "file transfer" portion of the server is already installed and working.

HNDSLFSV.AP can securely transact file transfers with several CHT file client applications. All secure clients require this server to set up a single, 2-part server-level login (accountid + password), to control file upload/download permissions.

HNDSLFCMD.APP is a CHT "Batch-Bot" upload/download application, enabling transfers into and out of the server root and any server subdirectory below the server root. "Batch-Bot" style applications may be used from the DOS command line, from DOS batch scripts, and, naturally, inside Clarion applications where they are known as "CHT Snap-Ins".

HNDSLFCL.APP is a simple, example client single-file uploader, downloader illustrating four different client-side upload/download methods.

CHTSNAPGET.EXE is a pre-compiled C# utility application included in the CHT Toolkit. It may be used to securely download files from this server when a server accountid:password combination is configured.

This HNDSLFSV.APP is entirely template-built and contains no significant hand-embedded code.

HNDSLFSVFX.AP can securely transact file transfers with several CHT file client applications. All secure clients require this server to set up a single, 2-part server-level login (username + password), to control file upload/download permissions.

HNDSLFCMD.APP is a CHT "Batch-Bot" upload/download application, enabling transfers into and out of the server root and any server subdirectory below the server root. "Batch-Bot" style applications may be used from the DOS command line, from DOS batch scripts, and, naturally, inside Clarion applications where they are known as "CHT Snap-Ins".

HNDSLFCL.APP is a simple, example client single-file uploader, downloader illustrating four different client-side upload/download methods.

This server is entirely template-built and contains almost no hand-embedded code. It may be used alone, via a standard HTTP communications link, or via an encrypted HTTPS tunnel communications link, when combined with a STUNNEL Proxy, configured with an SSL Certificate.

The IP's in this table were added in real time by our full-time running servers. The decision criteria are stored in a second table.

When a new IP attempts a connection, the IP table is first checked to determine if it is already blocked. The connection is terminated in the event that the IP is blocked.

If the IP is not already in our blocking table, or the IP is marked "WhiteList" then the connection is processed. At this point the connection's HTTP HEADER is checked for USER AGENT and COMMAND LINE.

If the user agent name string contains a value that has been established in our CHTBLOCKIPDEFS table as a filter value type (2), the incoming IP is rejected and closed. The IP is added to the CHTBLOCKIPFILTER table as a HARDBLOCK.

When the user agent name does NOT contain any suspect value the HTTP header is further processed to obtain the COMMAND LINE value. This is the actual request that the server is expected to process.

Should the COMMAND LINE contain any value established in the CHTBLOCKIPDEFS table as a filter value type (3), the incoming IP is rejected and closed. That IP is added to the CHTBLOCKIPFILTER table as a HARDBLOCK.

CHT wishes to avoid publishing the details of how this and our server blocking technology works so it will not appear as a web page or in any public or server-based help page or document.

Active subscribers with questions are encouraged to contact us by email at their
convenience: support@cwhandy.ca

* JumpStartBulkFileCompressExpandWithProgress
-- Bulk files compress/expand + encrypt/decrypt
* JumpStartBulkFileContainerizeWithProgress
-- Compress/Encrypt files to CHT .HZO container
* JumpStartBulkFileDeContainerizeWithProgress
-- Decrompress/Decrypt files from .HZO container
* JumpStartBulkFileCopyWithProgress
-- Bulk files copy to a target directory
* JumpStartBulkFileEncryptDecryptWithProgress
-- Bulk files encrypt/decrypt + compress/decompress
* JumpStartBulkFileDeleteWithProgress
-- Bulk files remove/erase/delete
* JumpStartBulkFileMoveWithProgress
-- Bulk files move/reposition
* JumpStartBulkFileRenameWithProgress
-- Bulk files rename/re-extension

A query allows you to describe the files to be acted on. Or files to be acted on may be selected from a file lookup dialog by double clicking the provided query text control.

The HNDOfficeWord class is introduced to the procedure via a template called EmbedHndWordClassFunctions. Then a second template called HandyWordInterfaceControls has been added to the main window to illustrate a variety of functions available.

This application is a work in progress intended to illustrate various capabilities and concepts having to do with MS Word interaction from Clarion applications.

CHTSNAP2PDF.EXE (AKA: CHT Snap To PDF), is a command-line translation tool that is able to translate well-formed HTML 5 documents into exact-copy PDF documents that include full use of correctly formatted internal and external links.

CHTSNAP2PDF.EXE requires no pre-configuration and has no DLL dependencies in this version or later. It can be run from the DOS prompt, from a standard Windows short cut or from inside a Clarion application. A number of CHT demo and utility applications, for example HNDDOCUMENTBUILDER make extensive use of this document translation application.

CHTSNAP2PDF.EXE can be incorporated into your application from the CHT Snap-In interface where you can find a "CHTSnap2PDF" option. Our template sets an IDE directive to copy the CHTSNAP2PDF.EXE into your application's compile directory. The template also enables a CHT Class called HNDSNAPCALL which contains functions for calling the editor from your application.

For DEMO application which incorporate CHTSNAP2PDF.EXE as described above, see HNDDOCUMENTBUILDER.APP, HNDPREVIEWER.APP and HNDTPXHTNEXT.APP. These applications are described here: HNDDOCUMENTBUILDER.APP.

Contact CHT at: support@cwhandy.ca for price and availability of C# source code information.

Gus M. Creces
The Clarion Handy Tools Page
http://www.cwhandy.ca
http://web.cwhandy.ca

CHT Snap Disk does not require any kind of pre-configuration involving a configuration dialog or maintaining registry entries

These DOS command-line inputs are required to use CHT Snap Disk.

** CHTSNAPDISK.EXE ** - Version: [27.00.00] **
© 1996-2023 CHT (Clarion Handy Tools) - www.cwhandy.ca

* The following 10 separate DOS command-line inputs are required
* to obtain disk or processor information.
-------------------------------------------------
* (1) To display CHTSNAPDISK.EXE instructions to console:
CHTSNAPDISK --HELP, -HELP, OR HELP
-------------------------------------------------
* (2) To display full disk information to console:
CHTSNAPDISK --INFO, -INFO, OR INFO
-------------------------------------------------
* (3) To generate full disk information to file, chtsnapdisk.txt:
CHTSNAPDISK --LIST, -LIST OR LIST
-------------------------------------------------
* (4) To generate full disk information to file, chtsnapdisk.txt:
* and open with chtsnapedit.exe:
CHTSNAPDISK --LISTEDIT, -LISTEDIT OR LISTEDIT
-------------------------------------------------
* (5) To display processor unique ID to console:
CHTSNAPDISK --PROCESSOR, -PROCESSOR OR PROCESSOR
-------------------------------------------------
* (6) To change the LABEL of the given drive number:
* Drive 0 is assumed if [OPT] "DrvNUM" is omitted.
CHTSNAPDISK --LABEL, -LABEL OR LABEL "LABEL HERE" [DRVNUM]
-------------------------------------------------
* (7) To display free space values of all drives:
CHTSNAPDISK --FREE, -FREE OR FREE
-------------------------------------------------
* (8) To see Clarion 10 registry values use
CHTSNAPDISK --C10DRIVE INFO
-------------------------------------------------
* (9) To see Clarion 11 registry values use
CHTSNAPDISK --C11DRIVE INFO
-------------------------------------------------

** CHTSNAPDISK.EXE ** - Version: [27.00.00] **
© 1996-2023 CHT (Clarion Handy Tools) - www.cwhandy.ca

Contact CHT at: support@cwhandy.ca for price and availability of C# source code information
or customer-specific customization of the executable.

Gus M. Creces
The Clarion Handy Tools Page
http://www.cwhandy.ca
http://web.cwhandy.ca

CHT Snap Edit requires no pre-configuration and has no DLL dependencies in this version or later. It can be run from the DOS prompt, from a standard Windows short cut or from inside a Clarion application. A number of CHT demo and utility applications, for example HNDDOCUMENTBUILDER make extensive use of this editor application.

This editor is branched from the same C# source code from which the Clarion IDE code editor was originally built. In fact, if you view Clarion source .CLW files from this editor, editing will feel familiar. The hot keys provided, however, are optimized for editing raw HTML and XML files.

Hot keys are provided for most of standard mark-up operations such as BOLD, ITALIC Paragraph, Image Links, Web Anchors and numerous others.

CHTSNAPEDIT.EXE can be incorporated into your application from the CHT Snap-In interface where you can find a "CHT Snap Edit" option. Our template sets an IDE directive to copy the CHTSNAPEDIT.EXE into your application's compile directory. The template also enables a CHT Class called HNDSNAPCALL which contains functions for calling the editor from your application.

Two procedure-local templates called SNAPEDITSTARTBUTTON, RUNCHTSNAPEDIT provide an easy way to incorporate various text, HTML or XML editing tasks into a Clarion Window procedure.

For DEMO application which incorporate CHTSNAPEDIT.EXE as described above, see HNDDOCUMENTBUILDER.APP, HNDBULKMAILBATCHER.APP and HNDBULKNETMAILPROMO.APP. These applications are described here: HNDDOCUMENTBUILDER.APP.

Contact CHT at: support@cwhandy.ca for price and availability of C# source code information
or customer-specific customization of the executable.

Gus M. Creces
The Clarion Handy Tools Page
http://www.cwhandy.ca
http://web.cwhandy.ca

CHTSNAPGET.EXE is added as a component to your Clarion application, from the CHT's global "Application Snap-Ins" template. A procedure-local template called SNAPGETSTARTBUTTON provides an easy way to configure the application two different ways from a Clarion window procedure and to trigger download of a file named in a procedure entry field.

CHTSNAPGET.EXE can also be used directly from the DOS command-line or in a DOS BATCH script.

For a DEMO application, see HNDTESTCHTSNAPGET.APP. That application is described here: DOCS FOR HNDTESTCHTSNAPGET.APP.

These DOS command-line inputs are required to fetch a remote file:

** CHTSNAPGET.EXE ** - Version: [27.00.00] **
© 1996-2023 CHT (Clarion Handy Tools) - www.cwhandy.ca

* These DOS command-line inputs are required to fetch a remote file:

CHTSNAPGET --FETCH FILENAME.EXT
CHTSNAPGET --FETCHUZ FILENAME.ZIP (TO UNZIP ON RECEIPT OF .ZIP FILE)

* FILENAME must be the raw name, no path, e.g. "myfile.pdf".
* Remote subdirectories are configured in the setup dialog.
* Wild card file names are not permitted. URL processing is stopped.
* This application must be configured before use.
* Configure manually via the command line, or by programmatically
* completing registry values with Clarion HNDSnapCall.CHTSnapGetConfig()
* in CHT class function (HNDSNAPCALL.INC/.CLW).
* To configure directly from the DOS command line, type:

CHTSNAPGET --CONFIG

* On the config dialog provided, complete the value fields.

** CHTSNAPGET.EXE ** - Version: [27.00.00] **
© 1996-2023 CHT (Clarion Handy Tools) - www.cwhandy.ca

Contact CHT at: support@cwhandy.ca for price and availability of C# source code information
or customer-specific customization of the executable.

Gus M. Creces
The Clarion Handy Tools Page
http://www.cwhandy.ca
http://web.cwhandy.ca

CHT Snap Mapi does not require any kind of pre-configuration involving a configurtion dialog or maintaining registry entries. All information required for any individual email-send task can be passed on the application command line, since the installed email client is already pre-configured.

CHTSNAPMAPI.EXE is added as a component to your Clarion application, from the CHT's global "Application Snap-Ins" template. A procedure-local template called SNAPMAPISTARTBUTTON provides an easy way send MAPI email from a Clarion window procedure.

For a DEMO application, see HNDTESTCHTSNAPTOOLS.APP. That application is described here: DOCS FOR HNDTESTCHTSNAPTOOLS.APP.

CHTSNAPMAPI.EXE accepts DOS command-line inputs in order to send text or HTML emails.

Three or four command-line inputs are required:

** CHTSNAPMAPI.EXE ** - Version: [27.00.00] **
© 1996-2023 Clarion Handy Tools - www.cwhandy.ca

* Three or four command-line inputs are required
* in order to send text or html mail with optional attachments.

CHTSNAPMAPI "TO" "SUBJECT" "MESG.TXT OR MESG.HTML" ["ATTACH.FILE"]

* Inputs with spaces or extended characters must be surrounded by double quotes.
* Otherwise, inputs may be provided without surrounding double quotes.
* The omittable [ATTACH.FILE] paramter represents optional attachment file(s).
* Mail results are written to the DOS console.
* MESG.TXT, MESG.HTML and ATTACH.FILE may include full paths to
* different folder locations. Otherwise they are assumed in the Start-In folder.
* Multiple TO addresses may be separated by either semi-colons or commas.
* Multiple attachments may be separated by either semi-colons or commas.

** CHTSNAPMAPI.EXE ** - Version: [27.00.00] **
© 1996-2023 Clarion Handy Tools - www.cwhandy.ca

Contact CHT at: support@cwhandy.ca for price and availability of C# source code information or
for customer-specific customization of the executable.

Gus M. Creces
The Clarion Handy Tools Page
http://www.cwhandy.ca
http://web.cwhandy.ca

CHTSNAPSEND.EXE source code, because it is not in Clarion app format, is available from CHT via special request in the form of a C# wizard. Once imported as a project into Visual Studio, the developer can customize the application to his own specifications should that ever be necessary.

CHTSNAPSEND.EXE (AKA: CHT Snap Send), is an error-reporting tool which integrates, with your Clarion application via CHT templates. It is able to provide screen-snaps of error-causing procedure windows as well as lower-level error codes and error messages issued by the application when an error is encountered. CHTSNAPSEND greatly increases the accuracy of error reporting from applications as it eliminates most of the error-reporting steps that end-users are likely to have difficulties with.

CHT Snap Send email settings can be configued manually using its internal setup dialog, or by leveraging a Clarion application to write the necessary registry entries from our Snap-Ins template interface.

This application does not take command-line inputs. It is leveraged by CHT's Snap-In template interface provided globally on the CHTSNAPGET tab and procedure-locally on a procedure tab that appears when the global CHTSNAPGET tab is enabled.

The "CHT Snapsend" template element, when enabled, writes global SnapSend configuration entries to the Windows Registry in order to customize some of the actions and messages that CHT SnapSend performs and displays, while taking application screen snaps. Further, this template causes the auto-population of multiple instances of a procedure-level template (one per window procedure) called "ProcedureSnapins(HndTools)". ProcedureSnapins(HndTools) instances are de-populated when ApplicationSnapins(HndTools) is removed. See the docs for ProcedureSnapIns to discover the procedure-specific configurations that are possible with that auto-populated template.

EmbedSnapCall: This template may be used to attach to your application, at the procedure level, a CHT Code module containing a single class called HNDSnapCall. This extension creates a single, local instance of the HNDSnapCall Class which is used to call a variety of "CHT SNAP-IN" executable tools in a manner that resembles standard DLL calls, using parameter passing on the command line.

ProcedureSnapIns: On a procedure-by-procedure basis, this template allows the developer to optionally expose the state of procedure-local and global variables while the procedure is running. These variables are added into a text file that is sent via email along with the procedure-window snapshot taken by CHT SnapSend. This template is also the parent of a button template called "HandyWindowsStopStartSnapSendButton(HndTools)". That means the button template does not appear in the IDE's control templates list until ApplicationSnapins' "Enable?" switch is checked.

Contact CHT at: support@cwhandy.ca for price and availability of source code information.

Gus M. Creces
The Clarion Handy Tools Page
http://www.cwhandy.ca
http://web.cwhandy.ca

CHTSNAPSMTP.EXE (AKA: CHT Snap SMTP), is able to send email via SMTP protocol from any Windows system with an internet connection and a viable SMTP server. Even web-based email providers such as HOTMAIL, GMAIL and YAHOO may be leveraged by CHTSNAPSMTP since they provide also for unique SMTP setups. CHTSNAPSMTP can also send secure, encrypted email assuming that the SMTP server being accessed provides for it.

CHT Snap Get can be configued manually from the command line, or by leveraging a Clarion application to write the necessary registry entries. Once configured, to a specific SMTP server and account emails can be sent from the DOS command line.

CHTSNAPSMTP.EXE is added as a component to your Clarion application, from the CHT's global "Application Snap-Ins" template. A procedure-local template called SNAPSMTPSTARTBUTTON provides an easy way send SMTP email from a Clarion window procedure.

For a DEMO application, see HNDTESTCHTSNAPSMTP.APP. That application is described here: DOCS FOR HNDTESTCHTSNAPSMTP.APP.

These DOS command-line inputs are required to send text or HTML emails:

Three or four DOS command-line inputs are required
in order to send text or html mail with optional attachments:

** CHTSNAPSMTP.EXE ** - Version: [27.00.00] **
© 1996-2023 Clarion Handy Tools - www.cwhandy.ca

* Three or four DOS command-line inputs are required
* in order to send text or html mail with optional attachments:

CHTSNAPSMTP "TO" "SUBJECT" "MSG.TXT" OR "MSG.HTML" ["ATTACH.FILE"]

* Inputs with spaces or extended characters use double quotes.
* Otherwise, inputs may be provided without surrounding double quotes.
* Individual inputs must be separated by one or more spaces.
* ATTACH.FILE is optional. It represents optional attachment file(s).
* Multiple attachments may be separated with either semi-colons or commas.

* CHT Snap SMTP must be configured before mail can be sent.
* Type "CHTSNAPSMTP --config" at the DOS prompt to configure.

* Mail results are written to the console and to chtsnapsmtp.log.
* MSG.TXT or MSG.HTML and ATTACH.FILE [OPT] may include full paths to folders.
* Multiple TO addresses may be separated with either semi-colons or commas.
* Issue "--rcpt" alone on command line prior to sending for read-receipt.
* Issue "--norcpt" prior to sending to cancel read-receipt setting.

** CHTSNAPSMTP.EXE ** - Version: [27.00.00] **
© 1996-2023 Clarion Handy Tools - www.cwhandy.ca

Contact CHT at: support@cwhandy.ca for price and availability of C# source code information
or customer-specific customization of the executable.

Gus M. Creces
The Clarion Handy Tools Page
http://www.cwhandy.ca
http://web.cwhandy.ca

CHT Snap Zip does not require any kind of pre-configuration involving a configurtion dialog or maintaining registry entries. All information required for any individual "zipping" task can be passed on the application command line.

CHTSNAPZIP.EXE is added as a component to your Clarion application, from the CHT's global "Application Snap-Ins" template. Three procedure-local templates called SNAPZIPSTARTBUTTON, SNAPUNZIPSTARTBUTTON and SNAPZIPDIRSTARTBUTTON, provides an easy way to incorporate various zipping tasks into a Clarion Window procedure.

For a DEMO application, see HNDTESTCHTSNAPZIP.APP. That application is described here: DOCS FOR HNDTESTCHTSNAPZIP.APP.

These DOS command-line inputs are required to zip files or directories.

** CHTSNAPZIP.EXE ** - Version: [27.00.00] **
© 1996-2023 CHT (Clarion Handy Tools) - www.cwhandy.ca

* [ ZR -ZR --ZR ]
* The ZR parameter recurses \sourcepath\ subdirectories and requires 3 inputs.
* This produces a zip with folder names included inside the zip.
* The second input optionally includes a [\zippath\] to place the output zip.
* When no [\zippath\] is given, the zip file is created in the application
* "start-in" directory.
* The \sourcepath\ parameter used without a mask must end with a backslash.
* And [mask] is an optional wildcard (e.g. *.exe, hnd*.tps, myfile.tps)
* that filters \sourcepath\ input files.

CHTSNAPZIP --ZR [\ZIPPATH\]ZIPFILENAME.ZIP \SOURCEPATH\[MASK]

* [ ZZ -ZZ --ZZ ]
* The ZZ parameter ignores \sourcepath\ subdirectories and requires 3 inputs.
* It produces a flat zip without including folder names in the zip.
* The second input optionally includes a [\zippath\] for placement of the zip.
* When no [\zippath\] is given, the zip file is created in the application
* "start-in" directory.
* The "\sourcepath\" parameter used without a mask must end with a backslash.
* And [mask] is an optional wildcard (e.g. *.exe, hnd*.tps, myfile.tps)
* that filters \sourcepath\ input files.

CHTSNAPZIP --ZZ [\ZIPPATH\]ZIPFILENAME.ZIP \SOURCEPATH\[MASK]

* [ ZL -ZL --ZL ]
* The ZL parameter lists zip contents and requires 2 inputs.
* It produces a comma-delimited list of zip files for pickup by calling apps.
* When no [\zippath\] is given, the zip file is located in the application
* "start-in" directory.

CHTSNAPZIP --ZL [\ZIPPATH\]ZIPFILENAME.ZIP

* [ ZF -ZF --ZF ]
* The ZF paramter lists zip contents and requires 2 inputs.
* It produces a fully formatted list intended for easy reading
* at the DOS console.
* When no [\zippath\] is given, the zip file is located in the application
* "start-in" directory.

CHTSNAPZIP --ZF [\ZIPPATH\]ZIPFILENAME.ZIP

* [ UZ -UZ --UZ ]
* The UZ parameter unzips the zip file. It requires 3 inputs.
* When no [\zippath\] is given, the zip file is created in the application
* "start-in" directory.
* The \unzippath\ parameter used without a mask must end with a backslash.
* And [mask] is an optional wildcard (e.g. *.exe, hnd*.tps, myfile.tps)
* that filters zip-extracted output files.

CHTSNAPZIP --UZ [\ZIPPATH\]ZIPFILENAME.ZIP \UNZIPPATH\[MASK]"

** CHTSNAPZIP.EXE ** - Version: [27.00.00] **
© 1996-2023 CHT (Clarion Handy Tools) - www.cwhandy.ca

Contact CHT at: support@cwhandy.ca for price and availability of C# source code information or
customer-specific customization of the executable.

Gus M. Creces
The Clarion Handy Tools Page
http://www.cwhandy.ca
http://web.cwhandy.ca

This global template provides an interface to your application whereby several "Snap-In" or "Batch-Bot" components may be incorporated.

This application illustrates CHTSNAPEDIT.EXE and HNDMAILCDO.EXE.

CHT "Batch-Bots" like HNDMAILCDO.EXE provide various functionalies, that can be used standalone from the DOS prompt , from a DOS BATCH file, or programmatically from a Clarion application. The above "Snap-Ins/Batch-Bots" provide text editing and SMTP-style email, respectively.

Procedure-level button control templates are provided for each of the "Snap-In" executables in order to pass information to them and launch them from your application, seamlessly, just like dll-based procedures. Button templates are: SnapEditStartButton and BotCDOStartButton.

External binary dependencies: CHTSNAPEDIT.EXE, HNDMAILCDO.EXE and HNDCAPCON.DLL

This global template provides an interface to your application whereby several "Snap-In" or "Batch-Bot" components may be incorporated.

This application illustrates CHTSNAPEDIT.EXE and HNDMAILMAPI.EXE.

CHT "Batch-Bots" like HNDMAILMAPI.EXE provide various functionalies, that can be used standalone from the DOS prompt , from a DOS BATCH file, or programmatically from a Clarion application. The above "Snap-Ins/Batch-Bots" provide text editing and MAPI email, respectively.

Procedure-level button control templates are provided for each of the "Snap-In" executables in order to pass information to them and launch them from your application, seamlessly, just like dll-based procedures. Button templates are: SnapEditStartButton and BotMAPIStartButton.

External binary dependencies: CHTSNAPEDIT.EXE, HNDMAILMAPI.EXE and HNDCAPCON.DLL

This application illustrates CHTSNAPEDIT.EXE and HNDMAILSMTP.EXE.

CHT "Batch-Bots" like HNDMAILSMTP.EXE provide various functionalies, that can be used standalone from the DOS prompt , from a DOS BATCH file, or programmatically from a Clarion application. The above "Snap-Ins" provide text editing and SMTP email, respectively.

Procedure-level button control templates are provided for each of the "Snap-In" executables in order to pass information to them and launch them from your application, seamlessly, just like dll-based procedures. Button templates are: SnapEditStartButton and BotSMTPStartButton.

External binary dependencies: CHTSNAPEDIT.EXE, HNDMAILSMTP.EXE and HNDCAPCON.DLL

HNDENCRYPT.EXE runs from the DOS prompt or it can be called from another application using Clarion RUN, or using CHT's HNDSNAPCALL Class, or from a Windows batch file or a windows .VBS script. It accepts several command line parameters that describe the input file and and output path.

HNDENCRYPT.EXE, is configured with a --KEY established saved and configured in the registry which is used in the encrypt operation. Files encrypted and decrypted on the same machine are processed easily.

Files passed to other machines must first configure the correct encryption key before they can decrypt files passed to them.

External binary dependencies: HNDENCRYPT.EXE and HNDCAPCON.DLL

CHT "Batch Bot", HNDZIPNET.EXE, is a command-line zip tool to zip files alone, or in bulk, using a DOS-style file mask to describe the files to be zipped. The application can be called from one of your Clarion applications, using RUN() or CHT class, HNDSNAPCALL, or a Windows batch file, or a Windows .VBS script to provide reliable single and multi-file zipping services.

This "test" application presents a BotZipStartButton template a target zip field, a source directory name, zip mask field, zip query field and an unzip target directory field. Complete the necessary fields and click the --zip button or the --unzip button.

HNDZIPNET.EXE error messages, warnings and help information from HNDZIPNET.EXE appear in a window text control to tell you the outcome of pushing the zip button.

External binary dependencies: HNDZIPNET.EXE, HNDCAPCON.DLL AND HNDNETZIPPER.DLL

This global template provides an interface to your application whereby several "Snap-In" and "Batch-Bot" components may be incorporated.

This application illustrates incorporating HNDSEARCH.EXE into a Clarion application using CHT's HNDSNAPCALL class.

CHT "Batch-Bots" like HNDSEARCH.EXE provide various functionalies, that can be used standalone from the DOS prompt , from a DOS BATCH file, or programmatically from a Clarion application. The above "Snap-In" provides text file search and replace capability.

Procedure-level button control templates are provided for each of the "Snap-In" executables in order to pass information to them and launch them from your application, seamlessly, just like dll-based procedures. Button templates are: BotSEARCHStartButton.

External binary dependencies: HNDSEARCH.EXE, CHTSNAPEDIT.EXE and HNDCAPCON.DLL

HNDMAKEHZO.EXE builds compressed/encrypted file containers based on Clarion .TPS files. These file containers (.HZO extension) may be used like zip files, except they are relational, making them easy to browse, add to, or extract from in a non-sequential access fashion.

HNDMAKEHZO.EXE, runs from the DOS prompt or can be called from another application such as this one using Clarion RUN, or CHT's HNDSNAPCALL class, or from a Windows BATCH file or windows .VBS script.

External binary dependencies: HNDMAKEHZO.EXE and HNDCAPCON.DLL

This global template provides an interface to your application whereby several "Snap-In" and "Batch-Bot" components may be incorporated.

This application illustrates CHTSNAPEDIT.EXE and HNDMAILNET.EXE.

CHT "Batch-Bots" like HNDMAILNET.EXE provide various functionalies, that can be used standalone from the DOS prompt , from a DOS BATCH file, or programmatically from a Clarion application. The above "Snap-Ins/Batch-Bots" provide text editing and SMTP email, respectively.

Procedure-level button control templates are provided for each of the "Snap-In" executables in order to pass information to them and launch them from your application, seamlessly, just like dll-based procedures. Button templates are: SnapEditStartButton and BotNetSMTPStartButton.

External binary dependencies: CHTSNAPEDIT.EXE, HNDMAILNET.EXE, HNDNETSMTP.DLL and HNDCAPCON.DLL

External binary dependencies: HNDSLFCMD.EXE and HNDCAPCON.DLL

CHTSNAPCRYPT.EXE is a command-line utility with which to encrypt files (to .HYN extension) and optionally wrap the encrpted file into a .ZIP.

CHTSNAPCRYPT.EXE is configured with a --KEY established saved and configured in the registry which is used in the encrypt operation. Files encrypted and decrypted on the same machine are processed easily.

Files passed to other machines must first configure the correct encryption key before they can decrypt files passed to them.

External binary dependencies: CHTSNAPCRYPT.EXE and HNDCAPCON.DLL

CHTSNAPDISK.EXE is a command-line disk-drive information utility which provides: Drive Number, Drive Letter, Drive Type, Volume Label, File System, Space Available to Current User, Total Space Available, Total Size of Drive, and Disk Hardware Serial with the "--info" command.

The "--list" command provides a file called "chtsnapdisk.txt" containing the above information.

The "--listedit" provides a file called "chtsnapdisk.txt" containing the above information and on completion, opens the file with CHTSNAPEDIT.EXE.

The "--processor" command also identifies the current computer's processor ID.

The "--label" command provides for changing the disk-drive label.

External binary dependencies: CHTSNAPDISK.EXE, CHTSNAPEDIT.EXE and HNDCAPCON.DLL

CHTSNAPGET.EXE is a command-line utility to download files from any CHT file server. It uses either the HTTP or HTTPS protocol.

CHTSNAPGET.EXE also has secure-file access capabilities. This requires user knowledge of the user-name/password combination protecting the file or files being downloaded. This secure mode can optionally use HTTPS protocol or HTTP protocol depending on server configuration.

File and HTTP header data, regardless of protocol, is encrtyped on request.

This application can be tested with CHT demonstration servers HNDSLFSV.APP or HNDFILSV.APP available in your \HNDAPPS\ directory.

External binary dependencies: CHTSNAPGET.EXE and HNDCAPCON.DLL

This global template provides an interface to your application whereby several "Snap-In" components may be incorporated.

This application illustrates CHTSNAPEDIT.EXE and CHTSNAPMAPI.EXE.

CHT "Snap-Ins" are C# executables (EXE's) which provide various functionalies, that can be used standalone from the DOS prompt , from a DOS BATCH file, or programmatically from a Clarion application. The above "Snap-Ins" provide text editing and SMTP email, respectively.

Procedure-level button control templates are provided for each of the "Snap-In" executables in order to pass information to them and launch them from your application, seamlessly, just like dll-based procedures. Button templates are: SnapEditStartButton and SnapSMTPStartButton

External binary dependencies: CHTSNAPMAPI.EXE, CHTSNAPEDIT.EXE and HNDCAPCON.DLL

This global template provides an interface to your application whereby several "Snap-In" components may be incorporated.

This application illustrates CHTSNAPEDIT.EXE and CHTSNAPSMTP.EXE.

CHT "Snap-Ins" are C# executables (EXE's) which provide various functionalies, that can be used standalone from the DOS prompt , from a DOS BATCH file, or programmatically from a Clarion application. The above "Snap-Ins" provide text editing and SMTP email, respectively.

Procedure-level button control templates are provided for each of the "Snap-In" executables in order to pass information to them and launch them from your application, seamlessly, just like dll-based procedures. Button templates are: SnapEditStartButton and SnapSMTPStartButton

External binary dependencies: CHTSNAPSMTP.EXE, CHTSNAPEDIT.EXE and HNDCAPCON.DLL

CHTSNAPZIP.EXE is a command-line utility that auto-zips a target directory while OPTIONALLY including any sub-directories of the source directory. CHTSNAPZIP.EXE also unzips to a target directory. This application illustrates how to do all of those things from inside a Clarion application using CHT Templates to write the code.

This application presents a SnapZipStartButton template and two input fields, a target zip file name field and a source directory name field. Complete these two fields and click the zip start button.

Other related templates used are SnapZipDirStartButton and SnapUnZipStartButton.

CHTSNAPZIP.EXE warns if the target zip file exists and if the source directory doesn't exist. Messages from CHTSNAPZIP.EXE appear in a window text control to tell you the outcome of pushing the zip button.

External binary dependencies: CHTSNAPZIP.EXE and HNDCAPCON.DLL

It drops a single "Spell Check" button onto your window to trigger spell-checking in entry and text controls populated on the procedure window. Checking can be triggered for the entire window using the button provided or individual controls can be checked using a configurable hot key.

Further, individual words may be checked by selecting the word and using a configurable hot key. Initially we are providing, on request, lexicons for the following languages: English, Afrikaans, Croatian, French, German, Greek, Italian, Netherlands, Portugese, Russian, Spanish, Swedish, Ukranian.

Since these lexicons are derived from open-source word lists, we will ask developers seeking non-English dictionaries to help us develop a common-words list for their chosen language. A common-words list is a set of the top 25-50 most commonly used words. In English, for example, these are words like "the", "and", "to", and so forth.

Four dictionaries are presently available: English, French, Afrikaans, and Portugese. Aside from English, we chose to release these languages first because developers contacted us and specifically encouraged us to do so.

If you speak and work in any of the above listed, but not-yet-implemented langauges, feel free to contact us and encourage us to give priority to your language in an upcoming build.

It drops a local spell check template called LocalIncludeSpellingCheck onto your window to trigger spell-checking in entry and text controls populated on the procedure window. Checking can be triggered for the entire window using CtrlF7 (reconfigurable) or individual controls can be checked using another configurable hot key.

Further, individual words may be checked by selecting the word and using a configurable hot key. Initially we are providing, on request, lexicons for the following languages: English, Afrikaans, Croatian, French, German, Greek, Italian, Netherlands, Portugese, Russian, Spanish, Swedish, Ukranian.

Since these lexicons are derived from open-source word lists, we will ask developers seeking non-English dictionaries to help us develop a common-words list for their chosen language. A common-words list is a set of the top 25-50 most commonly used words. In English, for example, these are words like "the", "and", "to", and so forth.

Four dictionaries are presently available: English, French, Afrikaans, and Portugese. Aside from English, we chose to release these languages first because developers contacted us and specifically encouraged us to do so.

If you speak and work in any of the above listed, but not-yet-implemented langauges, feel free to contact us and encourage us to give priority to your language in an upcoming build.

Settings include, the ability to:
1) establish the auto-backup timer,
2) modify the target backup directory,
3) modify the target zip directory
4) modify the target restore directory
5) maintain, delete and zip backup files
6) locate and restore backup files from zip

From this application you are able to select a range of backups and compress them into a single zip file for archiving to a configured location using HNDNETZIPPER.DLL

You are also able to search and examine zip archives and restore backed up applications and dictionaries to a configurable location.

This application now includes procedure(s) using the template CHTBestPracticeEmbedClass as an example for developers.
REQUIRES CHT #TIER2 TEMPLATES

Settings include, the ability to:
1) establish the auto-backup timer,
2) modify the target backup directory,
3) modify the target zip directory
4) modify the target restore directory
5) maintain, delete and zip backup files
6) locate and restore backup files from zip

From this application you are able to select a range of backups and compress them into a single zip file for archiving to a configured location.

You are also able to search and examine zip archives and restore backed up applications and dictionaries to a configurable location.

This specially named version (i.e. SNAP in the app name) is built on CHTSNAPZIP.EXE incorporated as a CHT "Snap-In" on the global template "ApplicationSnapins".

HNDBASE64CVT.EXE source code, because it is in Clarion .APP format, is included as a standard part of the CHT toolkit, provided both in .APP format as well as ready-to-run, in .EXE format.

The application accepts several command line parameters that describe the input file and output path. These parameters are as follows:

--help
    [OPT] Displays a help screen. Writes hndbase64cvthelp.txt.
--input
    [REQ] Path and name of input file
--output
    [OPT] Output path only - local to this exe if omitted.
--mode
    [OPT] Encode or decode - defaults to encode if omitted.

The output file name is formatted from the input file with a .h64 extension. For example: test.pdf becomes testpdf.h64

Rather than writing a program to perform a repetetive task such as zipping and uploading to an FTP site or sending an email announcement, HNDBATCHRUNNER.EXE lets you quickly write a script, save it to disk and execute the script when needed.

"Batch Bots" include a number of command-line utilities that at time of writing are as follows:

HNDBASE64CVT.EXE (Base 64 encoder/decoder)
HNDENCRYPT.EXE (File encrypter/decrypter)
HNDMAKEHZO.EXE (CHT Container builder)
HNDFTPNET.EXE (.NET-based FTP utility)
HNDMAILCDO.EXE (Windows CDO email send)
HNDMAILNET.EXE (.NET based SMTP email send)
HNDMAILSMTP.EXE (SMTP-based email send)
HNDMAILMAPI.EXE (MAPI-based email send)
HNDZIPNET.EXE (.NET-based file zip utility)
HNDSEARCH.EXE (Text file search/replace)
HNDSLFCMD.EXE (HTTP upload utility)
CHTSNAPGET.EXE (HTTP download utility)
CHTSNAPZIP.EXE (Zip, Unzip utility)
CHTSNAPSMTP.EXE (SMTP-based email send)
CHTSNAPMAPI.EXE (MAPI-based email send)
CHTSNAPEDIT.EXE (Clarion code + HTML editor)
CHTSNAPSEND.EXE (Error reporting utility)

All of the above (starting with HND) are provided to CHT developers pre-compiled as well as in source .APP format so they can be expanded, emulated or customized by CHT developers.

Many command-line utilities of this sort are available that perform a variety of useful tasks. For example:
CLARIONCL.EXE (Clarion generate/compile utility)
SIGNCODE.EXE (Windows code-signing utility)
REGASM.EXE (.NET assembly registration utility)

HNDBATCHRUNNER.EXE supports writing, storing, searching and executing of batch file scripts that support your day-to-day use of command-line utiliites of the sort described above.

Select a target directory containing several to-be-signed .EXE, .DLL or .OCX files; click select all, followed by the bulk sign button, and watch as in a few seconds the entire batch is signed with your designated code signing certificate.

Log files (*_SIGN.LOG) are created to document each executable as it is signed. If any single executable fails signing, an err file (*_SIGN.ERR) is created indicating what went wrong.

With CHT Clarion Project Builder you can perform the following operations directly without having to open your applications to change their internal configuration settings:

a) Switch between EXE and DLL compilation
b) LARGE_ADDRESS, DYNAMIC_BASE, DEP to .EXP
c) Change link mode from LIB (library) to DLL
d) Switch between Debug and Release mode
e) Switch between expire and no-expire mode
f) Switch from HNDFBACK.TRN / HNDCUSTOM.TRN
g) Adjust processor affinity of the EXE
h) Code Sign executable with developer certificate
i) Export the app to TXA
j) Copy executable to a configured target directory
k) Stop compilation on error or continue to next
l) Generate app discovery HTML to target path
m) View compile log for application with full details

CHT Clarion Project Builder requires that the HNDTOOLS.TPL (template) be present in your Clarion template directory and a CHT template called HNDCMPControlPanel has been applied to your applications. This template and file are supplied only to full-fledged CHT subscribers.

Prior to 2012, when CHT shipped a HNDFBACK.TRN (CHT Classes Translation File) that contained some new variables, it was the responsibility of the developer to copy these new variables to their personal HNDCUSTOM.TRN to avoid missing-variable errors during compilation.

This application automates that once manual process.

By opening this application and importing their HNDCUSTOM.TRN under the appropriate language menu, developers are able to generate a revised version of their own HNDCUSTOM.TRN which merges their personal HNDCUSTOM.TRN translations with the latest version of HNDFBACK.TRN.

Already-translated variables replace the English language versions and new variables are present and marked as "NEW" to make them easy to find for subsequent translation from the interface provided in this application.

After merging, and generating a new HNDCUSTOM.TRN based on a combination of their already-translated variables and new ones from HNDFBACK.TRN, developers are able to continue using their own HNDCUSTOM.TRN without having to manually synch new variables to avoid compilation errors.

NOTE: A POLISH translation category was added as of October, 2020.

Our CHT Toolkit installer/updater, for your Clarion version also assigns this application as the default Windows handler for .HZO files so that you can click on any .HZO file to open it and even unpack it to a target directory if the optional password is known. A CHT-style query allows you to describe the files to be containerized. Or files to be containerized may be dropped from MS Windows Explorer.

This application can be used to build standard .HZO installation and update files for transport and decontainerization by applications like HNDSETUPMKR.APP to provide continuous, on-line updating of your software and data products. HNDSETUPMKR.APP uses a new install-maker template to generate a custom web-installer using the .HZO containers created by this HNDSETUP.APP application.

This applicaton now incorporates three CHT-XSA security settings and a "Post File To Server" dialog, in order to make it quick and easy to upload your .HZO container to a waiting CHT installation server enabled with a CHT-XSA security dialog.

Start tracing by configuring the specific driver(s) used by your SQL application followed by a click on the "Minimize" button . Once this application is started, then start your SQL application.

Navigate in your SQL application to the specific area to be tested and bring HNDSQLTRACE.EXE back up using the windows task bar icon menu provided.

Manual tracing:
When HNDSQLTRACE.EXE re-appears all SQL statements executed to that point are displayed in reverse chronological order, with newest statements at the top. From this point forward, to trace specific actions, click the "Clear" button and interact briefly with your SQL application. Click the "Read Next" button to view the most recent SQL activity raised by your application. Repeat as necessary.

Automatic tracing:
Check the "Auto Trace" switch. A window timer will periodically refresh to the latest SQL select or group of selects issued by your application.

File Trace or Direct Trace:
These modes are mutually exclusive.

File trace is performed by communicating with SQL trace information issued by Clarion's file drivers into a text file. In "File Trace" mode a developer can trace any and all SQL select outputs from various browses in an application as long as HNDSQLTRACE.EXE is started and configured before starting the application.

"Direct Trace" mode is performed by low-level communication, usually from a specific procedure under scrutiny. This mode requires one of CHT's browse templates to be configured to issue trace information during interaction with the user.

This application includes the template CHTBestPracticeEmbedClass as an example for developers to study.

HNDVIDEOJOURNAL.EXE was introduced to play more informal, videos intended to answer developer questions and to cover a broader range of topics related to the CHT Toolkit.

The player is built on CHT Template HandyComMediaControl which uses the Windows Media Player COM object based in WMP.DLL.

The player is capable of playing off-line any videos which have been previously viewed to completion. On-line viewing of uncached videos begins quickly, once approximately 5 percent of the video has downloaded, and already-cached videos begin immediately since they are not downloaded again.

If you plan to adapt this application to act as a video player for your own videos, a useful, accompanying application called HNDBUILDVIDEOLIST.APP can build video index files on your CHT-based video server, of the type utilized by this application and by the HNDWindowsMediaPlayer class (HNDWMP.INC, HNDWMP,CLW, HNDWMP.TLB).

The CHT toolkit has evolved away from HTML techniques that rely heavily on external libraries of any kind, specifically Javascript libraries and CSS libraries.

HNDBRWCL.EXE has for 15 years or more, been a client that dislays interactive pages issuing from a CHT Type 1 Server. That is, a server which delivers data wrapped up in Javascript objects incorporating formal 3rd party Javascript libraries and 3rd party CSS (Cascading Style Sheet) libraries.

Since 2019 we've been producing our own self-contained HTML pages which use no Javascript or external CSS libraries. The pages are generated by Clarion applications using a technique we developed (all rights reserved) called CHT XML2HTML. Presently 100 percent of our website pages are created by ourselves using only CHT applications built with our tool kit, accessing web servers also of our own creation using only Clarion, plus the CHT toolkit.

In 2020 we began to purge from the CHT templates and classes all code using TYPE 1 server techniques. This purge-the-old, replace-with-new work continues to this day.

With the release of this interim "News" application, still called HNDBRWCL.EXE, we make a final break with the TYPE 1 Data Interactive Web Server as it has been for many years and make official our intention to develop a forum application based solely on our CHT XML2HTML techniques.

If you wish to know more about what our XML2HTML looks and acts like in the form of a useful, interactive web browse, visit the following CHT server:

https://templates.cwhandy.ca/.

The "Type" column in this browse links to other CHT XML2HTML documents interactively, to display template-specific documentation for any item clicked.

No Javascript here, no external CSS, just pure data-interactive HTML generated by CHT applications using CHT templates and classes.

Generate HTML Mail With Internal Style Sheets
It is important for HTML email to use internal style sheets so that the email, on arriving in the recipient's inbox, does not need to request external style sheets from the web. It is therefore deemed "safe" by email clients and it displays immediately, like text mail, without the user needing to click any kind of "allow" switch.

Style Sheet Generating Template
This application illustrates several "_mail_" XML2HTML example templates that allow the developer to change every important aspect of numerous useful HTML style sheets so that different "looks" can easily be incorporated into different HTML-generating-procedures. To create HTML outputs with new and different looks, simply copy the existing example procedure and add your own CSS styles (or modify ours) by adjusting template switches and by removing or adding to the various "sections" incorporated into our examples.

Select Single Or Multipe Email Addresses
Select one or more email addresses from the email browse(s) using standard MS Windows record marking and an .HTML file written ahead of time using CHTSNAPEDIT.EXE or generated by one of this application's "AutoGen" procedures.

A batch file is generated, which in a loop, successively calls HNDMAILSMTP.EXE or CHTSNAPSMTP.EXE (depending which one you choose to use) to send the HTML email body to the addresses selected above. The batch file may be run either from the DOS prompt or from a simple desktop link or from inside your own Clarion applications, or using CHT's HNDBATCHRUNNER.EXE. utility.

An example of this run-from-Clarion concept, is provided in the "Run (Send Mail With) Last Generated Batch Script" menu of this application.

CHT Bulk Mail Batcher is able to import email addresses exported from other applications such as Windows Live Mail.

Preconfigure your SMTP email-send account beforehand and select that account for sending before generating your batch file.

To create a PDF of any HTML document generated by CHT HTML Document Builder, just print it to disk with Windows native PDF printer driver. Better yet, use CHTSNAP2PDF.EXE to render an accurate PDF version of your HTML document including active web links that still work from PDF.

Style Sheet Generating Template
This application illustrates a new template that allows the developer to change every important aspect of numerous useful HTML style sheets so that different "looks" can easily be incorporated into different HTML-generating-procedures.

To create HTML outputs with new and different looks, simply copy the existing example procedure and add your own style and flare by adjusting template switches and by removing or adding to the various "sections" incorporated into our examples.

Menus are provided to instantly set the previewer's window size to one of a variety of viewport sizes for common device sizes from small phones like the Apple iPhone to larger phones, tablets and, of course, Windows desktop.

Interacting with "CHT Document Builder" applications, like CHTSNAPEDIT.EXE and CHTSNAP2PDF.EXE, this application picks up an HTML directory location or URL from the command line passed to it from the calling application, and displays the HTML content just generated and provides a way to transform the HTML document into a PDF document.

This provides instant feedback relative to the the document changes just made.

Buttons are supplied:
1) to select and load another local HTML file
2) to print the currently loaded file to the print device (PRN, PDF) selected by the user from a printer select dialog.

A URL entry control is supplied with which a remote web-site HTML file may be loaded, displayed and printed.

This app picks up an HTML file name (with path) from the command line if you wish to utilize the app as a command-line utility using Clarion RUN() or from a batch file.

If you wish to import the display/print procedure PreviewPrintHTMLMain() into your application from our app, that's easy enough to do as well.

The application accepts several command line parameters to provide input and output values, or to call its internal configuration dialog.

CHT Snap-Edit calls this HTML generator from its "XML2HTML" menu in order to transform CHT XML template files into HTML for previewing, storage, transport and conversion to PDF.

This generator implementation can access and call remote procedures established in a CHT data server configured in the "Connect" menu to request data packages which are then merged into the HTML document.

** GENERATING **
--input [REQ]
Name of the XML input template file.

--output [OPT]
Name of the HTML output template file.

--prevw [OPT]
Preview HTML after generate.

--noprevw [OPT]
No preview HTML after generate.

** CONFIGURE DATA SERVER **
--config [OPT]
Configure remote data server for secure access.

** HELP **
--help [CFG]
Pops up a splash help screen.

The application can be pre-configured using up to 20 potential configurations to back up a particular directory using a CHT Query that describes the files to be backed up, resulting in a standard zip file that can include source subdirectories right inside the zip.

This application's configuration button reminds only that MAPI email leverages the default email client to send mail, so it is only necessary that a working email client (e.g. Windows Live, Outlook) be present in order for email sending to operate correctly.

Once configured, your application can build a zip with one button click and send it to one or more recipients with a second click. Up to twenty separate, unique configurations are retained for instant re-use.

The application can be pre-configured using up to 20 potential configurations to back up a particular directory using a CHT Query that describes the files to be backed up, resulting in a standard zip file that can include source subdirectories right inside the zip.

An SMTP/CDO configuration dialog lets you preconfigure up to three target SMTP servers to handle the sending of your email and zip attachment.

Your application can build a zip with one button click and send it to one or more recipients with a second click. Up to twenty separate, unique configurations are retained for instant re-use.

The application can be pre-configured using up to 20 potential configurations to back up a particular directory using a CHT Query that describes the files to be backed up, resulting in a standard zip file that can include source subdirectories right inside the zip.

Email configuration is carried out on the system's default MAPI client software. Success with this MAPI client is dependent on a MAPI-compliant email application being installed and configured on the hosting computer.

This application's email configuration button reminds only that MAPI email leverages the default email client to send mail, so it is only necessary that a working email client (e.g. Windows Live, Outlook) be present in order for email sending to operate correctly.

Your application can build a zip with one button click and send it to one or more recipients with a second click. Up to twenty separate, unique configurations are retained for instant re-use.

The application can be pre-configured using up to 20 potential configurations to back up a particular directory using a CHT Query that describes the files to be backed up, resulting in a standard zip file that can include source subdirectories right inside the zip.

An SMTP configuration dialog lets you preconfigure up to three target SMTP servers to handle the sending of your email and zip attachment.

Once configured, your application can build a zip with one button click and send it to one or more recipients with a second click. Up to twenty separate, unique configurations are retained for instant re-use.

The application can be pre-configured using up to 20 potential configurations to back up a particular directory using a CHT Query that describes the files to be backed up, resulting in a standard zip file that can include source subdirectories right inside the zip.

An SMTP configuration dialog lets you preconfigure up to three target SMTP servers to handle the sending of your email and zip attachment.

Once configured, your application can build a zip with one button click and send it to one or more recipients with a second click. Up to twenty separate, unique configurations are retained for instant re-use.

The application can be pre-configured using up to 20 potential configurations to back up a particular directory using a CHT Query that describes the files to be backed up, resulting in a standard zip file that can include source subdirectories right inside the zip.

An SMTP configuration dialog lets you preconfigure up to three SMTP servers to handle the sending of your email and zip attachment.

Once configured, your application can build a zip with one button click and send it to one or more recipients with a second click. Up to twenty separate, unique configurations are retained for instant re-use.

The application can be pre-configured using up to 20 potential configurations to back up a particular directory using a CHT Query that describes the files to be backed up, resulting in a standard zip file that can include source subdirectories right inside the zip.

This application's email configuration button reminds only that MAPI email leverages the default email client to send mail, so it is only necessary that a working email client (e.g. Windows Live, Outlook) be present in order for email sending to operate correctly.

Once configured, your application can build a zip with one button click and send it to one or more recipients with a second click. Up to twenty separate, unique configurations are retained for instant re-use.

The application can be configured to back up a variety of directories using a CHT File Query that describes the files to be backed up. The application produces a standard zip file that can optionally include source subdirectories right inside the zip.

The HTTP configuration dialog also lets you preconfigure the target CHT file server designated to accept your zip file(s).

This application utilizes CHT-XSA secure, encrypted authentication, so that you can authenticate against any CHT Server file server that has been provided with a CHT-XSA configuration dialog.

Once configured, your application can build a backup with one button click and PUT it to a CHT-Style secure XSA web server with a second click.