home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Monster Media 1993 #2
/
Image.iso
/
clipper
/
sx11c501.zip
/
SIX501.DOC
next >
Wrap
Text File
|
1993-06-18
|
6KB
|
122 lines
=========================================================================
SIx Driver v1.1c for Clipper 5.01a
=========================================================================
This patch file (SIX501.EXE) will update the SIx Driver v1.1b (Dated
03-25-93 or 03-30-93, 12:00a) to the Clipper 5.01a-compatible v1.1c
release (dated 06-18-93, 12:00a). This patch file will ONLY update
this v1.1b release!
The patch file will update the existing LIB, NG, and OBJ files and will
create new LNK and CH files.
To update your SIx Driver v1.1b to the Clipper 5.01a-compatible v1.1c
release, follow these steps:
1. Make sure that all the following SIx Driver v1.1b files are in the
directory to be updated:
DBFSIX.LIB DBT.OBJ DBCREATE.OBJ
DBFSIX.OBJ FGET.OBJ MACHSIX.OBJ
DBFSIX.NG MACHSIX.NG
2. Make sure that the SIX501.EXE patch file is in the same directory
as your SIx Driver files (listed above) and run it. It will update
the files listed above, and create new copies of all of the new
header (.CH) and link (.LNK) script files.
All of the old files will be renamed with a ($) at the end of the
file extension. For example, your old DBFSIX.LIB will be renamed
DBFSIX.LI$.
3. Now, copy the newly updated files (all of which will have a
date/time stamp of 06-18-93, 12:00a) to whichever directories you
need them in to work with Clipper 5.01a.
See the new NG files for specific details of what's new and different in
this release. Here's a short rundown of some of the primary additions
and changes in this release:
CHANGE IN USING MACHSIX !!
--------------------------
Changes have been made to the way MACHSIX is linked into your applica-
tion. To use MACHSIX with the SIx Driver, you must now include the
MACH6SIX.OBJ in your link script, as well as the MACHSIX.LIB file. The
change was made allow the same MACHSIX library to work with both DBFSIX
and our new product -- HiPer-SIx. When used with HiPer-SIx (DBFNSX.LIB)
you'd link in a file called MACH6NSX.OBJ instead. This will save code
size when you use DBFSIX and HiPer-SIx together. By the way, if you'll
be using _both_ DBFSIX and DBFNSX in the same application along with Mach
SIx, you'd link in both of the OBJ files (MACH6SIX.OBJ and MACH6NSX.OBJ).
ELIMINATION OF 5333 Errors !!
-----------------------------
Our engineers were able to track down and squash what we believe was the
source of 5333 errors in the SIx Driver. The problem turned up if the
application had either a large number of files open (around 150), or just
very large data files in general. If you were unfortunate enough to hit
5333 errors with the SIx Driver 1.1b, 1.1c should clear them up.
SUCCESSWARE ANNOUNCES NEW PRODUCT STABILITY GUARANTEE !!
--------------------------------------------------------
We here at SuccessWare feel so strongly about our 1.1c release of the SIx
Driver we are attaching a 'ROCK-SOLID' guarantee. If you discover a
reproducible bug and our engineers cannot fix the problem in 5 working
days, SuccessWare will refund your purchase price PLUS 10% for your
trouble. We are completely commited to producing rock solid drivers and
with the new guarantee we put our money where our mouth is.
100% PROTECTED MODE COMPATIBILITY
---------------------------------
SIx Driver 1.1c has been extensively tested using the new ExoSpace
protected mode DOS extender for Clipper. Our testing team has confirmed
that all of our test suite programs now run cleanly under ExoSpace. If
you decide to use this new technology, you can rest assured that the SIx
Driver will perform without problems.
Additions since the 1.1b release:
---------------------------------
In each release, we have continued to improve the SIx Driver. This release
is no exception.
1. Sx_CDXCheck() has been added to handle the behavior of opening tables
with structural .CDX files. By default if a .dbf file is marked as having
a structural .CDX file and the .CDX file does not exist, the .DBF is opened
and no error is generated. By passing a TRUE to Sx_CDXCheck() when a .DBF
file is opened it is marked as a having a structural .CDX file and the
.CDX file does not exist, an error (690) is generated. This allows for the
capture of the error in a custom ERRORSYS and the programmer can decide
what to do, such as rebuilding the tags.
2. Index Creation times have been improved by 30%.
3. 'F' Floating type are now handled correctly. These are no longer being
converted internally to numeric types. Since 'F' type is not supported in
other Clipper Drivers such as SDF and DELIM do not attempt a COPY TO or
APPEND FROM with Float types. All other types perform without error.
---------------------------------------------------------------------------
If you have any problems using this update patch, please contact
SuccessWare Tech Support or, if outside the USA, your local dealer or
distributor.
The full file set (non-patch) will be posted in the PRIVATE files area of
the BabelBoard BBS (909-694-6891) for all registered SIx Driver owners to
download, if required.
Thank You!
The SuccessWare Team