Utilities
MULTI-EDIT TEMPLATE..Template for Multi-Edit Professional Editor
X2CLIP.EXE...........Xbase to Clipper Interface for improved database performance
MEM2XPP.EXE..........Convert Clipper .MEM files to Xbase++ .XPP files
MULTI-EDIT TEMPLATE
Template for Multi-Edit Professional Editor
Description:
EXPRESS.TPT is a template file for use with Multi-Edit,the
programmer's editor. It contains templates for all eXPress++
commands and functions.
Just copy EXPRESS.TPT to your \MEW\CONFIG directory or whichever
directory contains your Multi-Edit templates.
When Multi-Edit is configured for "Space-Bar Expansion" of a
template, you can easily bring a template for any eXPress++
command into the text you are editing by typing the keyword for
the command followed immediately by a SPACE.
For example, if you are not sure of the syntax of the DCTABPAGE
command, simply type DCTABPAGE<þspaceþ>. The following will be
inserted into your text:
@ <þnSRowþ>,<þnSColþ> DCTABPAGE <þoGroupþ> ;
[SIZE <þnWidthþ>, <þnHeightþ>] ;
[TYPE <þnTypeþ>] ;
[TABHEIGHT <þnTabHþ>] ;
[PREOFFSET <þnPreþ>] ;
[POSTOFFSET <þnPostþ>] ;
[PARENT <þoParentþ>] ;
[GROUP <þnGroupþ>] ;
[CAPTION <þcTextþ>] ;
[CARGO <þxCargoþ>] ;
[MESSAGE <þcMsgþ>] ;
[HELPCODE <þcHelpCodeþ>] ;
[COLOR <þncColorþ> [,<þncDisabledþ>] ] ;
[WHEN <þbWhenþ>] ;
[FONT <þcFontþ>] ;
[HIDE <þbHideþ>] ;
[VALID <þbValidþ>] ;
[<þp: PIXELþ>] ;
[TOOLTIP <þcToolTipþ>] ;
[CURSOR <þnCursorþ>] ;
[RELATIVE <þoRelþ>] ;
[EVAL <þbEvalþ>] ;
[DATALINK <þbDataLinkþ>] ;
[ ID <þcIdþ> ]
Source/Library:
EXPRESS.TPT
X2CLIP.EXE
Xbase to Clipper Interface for improved database performance
Description:
X2CLIP.EXE is a Clipper 5.2e program which is used to run database
operations in the background. Some Xbase++ database operations,
such as reindexing, appending, etc. are too slow, therefore a
set of DC_XC*() functions is included in the DCLIPX.DLL library
to improve database performance as much as 20 times.
The files needed to build X2CLIP.EXE are X2CLIP.PRG and X2CLIP.LNK.
They are included in the \EXPRESS\SOURCE directory. When using
the XC_PROGRAM operation in a parameters array passed to
DC_XCCall(), the custom program must be written in Clipper, then
compiled and linked into the X2CLIP.EXE program by adding it to
the X2CLIP.LNK link script and re-linking the program with a
Clipper linker. The custom program receives a single parameter
which can be a multidimensional array of any type of information
which is compatabile with both Xbase++ and Clipper. This array
is stored in the XC_ARRAY_DATA element of the parameters array.
The X2CLIP.EXE program is called by the XBase++ program by a
call to DC_XCOpen() which runs the X2CLIP.EXE program in the
background. This program then runs a loop routine which waits
for instructions from the Xbase++ program via calls to DC_XCCall().
The X2CLIP.EXE program is synchronized to the Xbase++ program
through a system of data writes to a shared record in the
X2CLIP.DBF file.
Notes:
The X2CLIP.EXE program is intended to be called only by the
Xbase++ program using the RunShell() function launched in a
separate thread. It is passed a handle number and a default
directory. The handle number is the record number of X2CLIP.DBF
to use to pass data back and forth from the Xbase++ program to
the X2CLIP.EXE program. The default directory is the disk
directory containing the X2CLIP.DBF file. If the file does
not exist it will be created.
If the X2CLIP.EXE program fails to communicate with the Xbase++
program, it will stay in a loop indefinately or until the
ESCAPE key is pressed.
Examples:
MEM2XPP DISCLAIM.MEM
MEM2XPP ALL
Source/Library:
DC_XCOpen()
MEM2XPP.EXE
Convert Clipper .MEM files to Xbase++ .XPP files
Syntax:
MEM2XPP < MemFileName > | ALL
Arguments:
< MemFileName > is the name of a Clipper .MEM file to convert.
If the ALL argument is used, then all files with the .MEM
extension will be converted to .XPF files with the same
prefix.
Description:
MEM2XPP.EXE is an Xbase++ utility program that converts
Clipper *.MEM files to XBase++ *.XPF files. Xbase++ is
not compatible with Clipper .MEM files because they were
designed for 16-bit systems and are insufficiently
robust for the features of Xbase++. They must be
converted to .XPF files for the REST FROM <þmemfileþ>
command to work properly.
The original .MEM file is not altered in any way. A new
file with the same prefix as the original file is created
but with an extension of .XPF.
An additional file with the same prefix as the original
files but with an extension on .TXT is also created.
This is an ordinary text file that lists the memory
variables and contents of the memory file.
Examples:
MEM2XPP DISCLAIM.MEM
MEM2XPP ALL