This 6UTILS.

ZIP file contains all of the utility programs that are included with the SuccessWare Index Driver (SIx Driver) RDD. These programs are: CDXINFO.EXE DBCRE8.EXE DBFSTRU.EXE SEEK.EXE These programs can be freely copied and used by individuals royalty-free, with one exception. They cannot be packaged and distributed, individually or as a group, as part of another software product without prior written consent from SuccessWare. Questions and/or comments regarding these utilities should be directed to: SuccessWare 90, Inc. 27349 Jefferson Ave., Suite 101 Temecula, CA 92590 Voice: (909) (800) FAX : (909) BBS : (909) CIS : Loren 699-9657 (8am-5pm PST) 683-1657 (8am-5pm PST) 695-5679 (24 Hours) 694-6891 (24 Hours, N-8-1, 14.4 kbps) Scott [70274,2677]

-----------------------------------------------------------------------------CDXINFO.EXE: The CDXINFO utility will display the following information about a .CDX or .IDX index file: File Name File Type Tag Count CDXINFO will also display the following information about each tag in a .CDX index file, or for a single .IDX index file: Tag Name Expression Conditional Unique Status RYO Status

The command-line syntax for using CDXINFO.EXE is as follows: CDXINFO <FileName>[.CDX] Where: FileName = Name of the CDX/IDX file for which info is desired. Example: To Display information about tags in TEST.CDX: C:\> CDXINFO test

-----------------------------------------------------------------------------DBCRE8.EXE: Many of the sample programs included with the SIx Driver will require that you have created a TEST.DBF file for the example to use. We have provided you with a small utility called DBCRE8.EXE which you can use to quickly create a TEST.DBF file full of psuedo-random data. You can also optionally create an associated memo file in either the CA-Clipper (.DBT) or FoxPro (.FPT) formats. The structure of the database files created by the DBCRE8 utility is as follows: NAME ----------FIRST LAST STREET CITY STATE ZIP HIREDATE MARRIED AGE * SALARY ** NOTES TYPE ---C C C C C C D L N N C LEN DEC --- --20 20 30 30 2 10 8 1 2 0 6 0 70

(*) The SALARY field's DEC value becomes 2 if the /d switch is used. (**) If the /mD or /mF switch is used, this field will become a memo field (Type "M") with a length of 10. The command-line syntax for using DBCRE8.EXE is as follows: DBCRE8 <nRecs> [options] Where: <nRecs> = Number of records to add to the DBF file. Options: /d = Make SALARY field use <n> decimal places. ( Ex: /d3 ). The specified value can be from 1-4. The default is 2. /f = Optional DBF file name to create. Ex: /fBOGUS. The default data file name is TEST. /mD = Include MEMO field using DBT format. /mF = Include MEMO field using FPT format. An optional memo block size can also be set by immediately following the "F" with a colon followed by the desired block size. Ex: /mF:512 or /mF:16. This value must be a multiple of 16, between 16 and 1024. The default value is 64. NOTE: By default, no memo field is used.

Examples: Create TEST.DBF with 1000 records ...........: DBCRE8 1000 Create BOGUS.DBF with 500 records ...........: DBCRE8 500 /fBOGUS Create TEST.DBF and TEST.DBT with 100 records: DBCRE8 100 /mD Create FOO.DBF and FOO.FPT with 250 records .: DBCRE8 250 /mF /fFOO Create FOO.DBF and FOO.FPT w/ 32-byte blocks : DBCRE8 250 /mF:32 /fFOO Create TEST.DBF w/ 2 decimal places in SALARY: DBCRE8 1000 /d Create DEMO.DBF w/ 3 decimal places in SALARY: DBCRE8 1000 /d3 -----------------------------------------------------------------------------DBFSTRU.EXE: The DBFSTRU utility will display the following information about a database file: * Last Update Data Offset Record Size Num Records Memo Type (None, DBT, FPT, or Unknown) Structure

(*) - If an FPT memo file is being used, the memo-block size in use will also be displayed. DBFSTRU will also optionally create a CA-Clipper .PRG file which contains the source code for creating the specified database file, including any associated memo file of the proper type and memo-block size. The command-line syntax for using DBFSTRU.EXE is as follows: DBFSTRU <DBFname>[.DBF] [/p[<PrgName>]] Where: /p = Create a .PRG file with Clipper source code to create the specified .DBF file. ( Ex: /pTEST ). If no name is specified, STRU.PRG will be created. Examples: Display structure of TEST.DBF ...................: DBFSTRU test Display structure of TEST.DBF and create STRU.PRG: DBFSTRU test /p Display structure of TEST.DBF and create FOO.PRG : DBFSTRU test /pFOO -----------------------------------------------------------------------------SEEK.EXE:

The SEEK utility is very handy in making sure that the file you think your compiler and/or linker are using is the correct one. SEEK will look for the specified file in the specified (or assumed) DOS environment path. For example, if you think that your linker may be picking up an old version of your BOGUS.LIB file somewhere in your LIB path, SEEK will tell you. It will search your LIB path for the first BOGUS.LIB file that your linker would be using. If you're not sure which FOOBAR.CH file, CA-Clipper's preprocessor will be using, SEEK can tell you that as well. For obvious file extensions, there is no need to specify the environment path to search in, unless you want to force SEEK to look in a different environment path instead. For example, if the file extension is .h, .ch, or .inc, SEEK will assume it's a header file and scan the INCLUDE path. SEEK will also optionally: List ALL of the specified files that were found in the selected DOS environment path. Change to the drive and directory of the found file. Actually, for people who happen to nest their development files many levels deep, even when you know for sure which file is being used, this option can be used as a quick way to get to that directory. Copy the found file into the current directory. Display with a terse (single line, no title screen) output. This is mainly useful when using SEEK in a batch file to display large groups of file paths. The command-line syntax for using SEEK.EXE is as follows: SEEK <cFileName> [<cEnvPath>] [options] Where: <cFileName> = The file <cEnvPath> = Optional file in. defaults Options: to search for. environment path to search for the If no path is specified, obvious are assumed.

/a = Find all occurrences of specified file in path. /c = Copy the found file into the current directory. (Not available if /a switch is used.) /d = Change to the directory of the found file. (Not available if /a switch is used.) /t = Terse display (only show the SEEK result line)

Examples: SEEK BOGUS.LIB LIB SEEK STDIO.H INCLUDE SEEK TEST.EXE PATH SEEK BOGUS.LIB // Searches LIB // Searches INCLUDE // Searches PATH // Assumes LIB

SEEK BOGUS.LNK SEEK STDIO.H SEEK STD.CH SEEK DOIT.BAT

// Assumes LIB // Assumes INCLUDE // Assumes INCLUDE // Assumes PATH

// Search for TEST.EXE, but in the PRG environment path instead SEEK TEST.EXE PRG // Search for all MYUDC.CH files in INCLUDE path SEEK MYUDC.CH /a // Search for TEST.OBJ and copy it to the current directory SEEK TEST.OBJ /c // Search for DEMO.LIB, and change to the directory it's found in SEEK DEMO.LIB /d ------------------------------------------------------------------------------