FT_NTXHAND

FT_NTXHAND()
 Obtain the handle associated with an open .NTX file.

 Syntax

     FT_NTXHand( <nOrderNum> ) -> nHandle

 Arguments

    <nOrderNum> is a numeric value indicating the active index for which
    the handle is to be obtained.

 Returns

   The file handle, or zero if no .NTX is open in the specified
   work area or if <nOrderNum> does not represent an open index.

 Description

   For your own twisted reasons you may need make direct use of the
   file handle associated with an index.  This function gives you
   that capability, but use it with care and don't blame me if you
   botch something up.

   By default this function works on the current work area, but can be
   made to work on any work area through the use of the standard Clipper
   alias operator.

   Be aware that this function makes use of Clipper's internal work
   area information which is subject to change in future versions of
   Clipper.  If this makes you uncomfortable then don't use this function,
   you gutless weasel.

   This function is written to adhere to Turbo Assembler's IDEAL mode.
   To use another assembler, rearrange the SEGMENT and PROC directives
   and make any other necessary changes to the source code.

 Examples

     // Get the handle for the second index

     QOut( FT_NTXHand( 2 ) )

     // Try a non-current work area

     nHandle := THISFILE->( FT_NTXHand( 1 ) )

     // This will return zero because only 15 indexes can be active

     nHandle := THATFILE->( FT_NTXHand( 22 ) )

 Source: NTXHANDL.ASM

 Author: Ted Means

 

FT_DBTHAND

FT_DBTHAND()
 Obtain the handle associated with an open .DBT file.
------------------------------------------------------------------------------

 Syntax

     FT_DBTHand() -> nHandle

 Arguments

    None

 Returns

   The file handle, or zero if no .DBT is open in the specified
   work area.

 Description

   For your own twisted reasons you may need make direct use of the
   file handle associated with a memo field file.  This function gives you
   that capability, but use it with care and don't blame me if you
   botch something up.

   By default this function works on the current work area, but can be
   made to work on any work area through the use of the standard Clipper
   alias operator.

   Be aware that this function makes use of Clipper's internal work
   area information which is subject to change in future versions of
   Clipper.  If this makes you uncomfortable then don't use this function,
   you spineless jellyfish.

   This function is written to adhere to Turbo Assembler's IDEAL mode.
   To use another assembler, rearrange the SEGMENT and PROC directives
   and make any other necessary changes to the source code.

 Examples

     QOut( FT_DBTHand() )

     // Try a non-current work area

     nHandle := THISFILE->( FT_DBTHand() )

     // This will return zero if no database is open in work area 133

     select 133
     QOut( FT_DBTHand() )

 Source: DBTHANDL.ASM

 Author: Ted Means

 

FT_DBFHAND

FT_DBFHAND()
 Obtain the handle associated with an open .DBF file.

 Syntax

     FT_DBFHand() -> nHandle

 Arguments

    None

 Returns

   The file handle, or zero if no .DBF is open in the specified
   work area.

 Description

   For your own twisted reasons you may need make direct use of the
   file handle associated with a database.  This function gives you
   that capability, but use it with care and don't blame me if you
   botch something up.

   By default this function works on the current work area, but can be
   made to work on any work area through the use of the standard Clipper
   alias operator.

   Be aware that this function makes use of Clipper's internal work
   area information which is subject to change in future versions of
   Clipper.  If this makes you uncomfortable then don't use this function,
   you cowardly slug.

   This function is written to adhere to Turbo Assembler's IDEAL mode.
   To use another assembler, rearrange the SEGMENT and PROC directives
   and make any other necessary changes to the source code.

 Examples

     QOut( FT_DBFHand() )

     // Try a non-current work area

     nHandle := THISFILE->( FT_DBFHand() )

     // This will return zero if no database is open in work area 133

     select 133
     QOut( FT_DBFHand() )

 Source: DBFHANDL.ASM

 Author: Ted Means

 

File Terms

Binary File :

A file that contains an unformatted sequence of bytes. Carriage return, linefeed, or end of file characters have no special meaning in a binary file. Binary files include executable files, graphics files, or data files.

See Also: Text File

Delimited File :

A text file that contains variable-length database records with each record separated by a carriage return/linefeed pair ( CHR(13) + CHR(10) ) and terminated with an end of file mark ( CHR(26) ). Each field within a delimited file is variable length, not padded with either leading or trailing spaces, and separated by a comma. Character strings are optionally delimited to allow for embedded commas.

See Also: Database, SDF File, Text File

Directory :

The major operating system facility for cataloging files. A directory contains a list of files and references to child directories (subdirectories), and is identified by name. Directories can be nested forming a hierarchical tree structure. The operating system provides a number of facilities that allow users to create and delete directories.

See Also: Disk, File, Path, Volume

Drive :

A disk drive or a letter (normally followed by a colon) that designates a disk drive. On most computers, the letters A and B refer to floppy disk drives; other letters refer to fixed disk drives or logical drives (e.g., fixed disk partitions or network drives).

Extension :

A filename extension normally used for identifying the type or originating program of a file.

See Also: Drive, Filename, Path

File :

A file is an organized collection of bytes stored on disk, maintained by the operating system, and referenced by name. Its internal structure is solely determined by its creator.

See Also : Binary File, Database, Text File

File Handle :

An integer numeric value returned from FOPEN() or FCREATE() when a file is opened or created. This value is used to identify the file for other operations until it is closed.

Filename :

The name of a disk file that may optionally include a drive designator, path, and extension.

See Also: Drive, Extension, Path

Path :

A literal string that specifies the location of a disk directory in the tree structured directory system. A path specification consists of the following elements: an optional disk drive letter followed by a colon, an optional backslash indicating that the path starts at the root directory of the specified drive, the names of all the directories from the root directory to the target directory, separated by backslash () characters. Example: C:CLIPPERINCLUDE. A path list is a series of path specifications separated by semicolons.

SDF File :

A text file that contains fixed-length database records with each record separated by a carriage return/linefeed pair (CHR(13) + CHR(10)) and terminated with an end of file mark (CHR(26)). Each field within an SDF file is fixed-length with character strings padded with trailing spaces and numeric values padded with leading spaces. There are no field separators.

Separator :

The character or set of characters that differentiate fields or records from one another. In Clipper language, the DELIMITED and SDF file types have separators. The DELIMITED file uses a comma as the field separator and a carriage return/linefeed pair as the record separator. The SDF file type has no field separator, but also uses a carriage return/linefeed pair as the record separator.

See Also: Delimiter

Subdirectory :

See : Directory

Text File :

A file consisting entirely of ASCII characters. Each line is separated by a carriage return/linefeed pair (CHR(13) + CHR(10)) and the file is terminated with a end of file mark (CHR(26)).

See Also: Delimited File, Program File, SDF File

Volume :

A unit of disk storage uniquely identified by a label and of fixed size. A hard disk can be partitioned into one or more volumes by an operation system utility. Volumes are subdivided into one or more directories organized in tree structure.

See Also: Directory, Disk