Click above to get retro games delivered to your door ever month!

   This chapter will discuss two different topics: Injection Points and
   Reverse Engineering. These give the programmer freedom to manually
   intervene on the logical flow of the sources created. In this way, the
   application is left open for any customisation on the standard source
   generated by dBsee.

   dBsee allows for three levels of intervention:

Standard Template

   This solution is appropriate whenever it is necessary to modify the
   generated sources to adapt it to the company's standard.

   The installation procedure of dBsee creates, among the different
   directories, the \DBSEE4\TMP sub-directory. This directory contains the
   start-up project's repository, i.e. the base of every new project (BIN and
   EXE sub-directories). It also contains the CLIPPER5 sub-directory, which
   holds all the template files supplied with dBsee.

     . The BIN sub-directory contains the start-up project's
       repository.

     . The EXE sub-directory contains the configuration files for
       the generated application.

     . The CLIPPER5 sub-directory contains three type of template
       files:
        The templates with a DLG extension are use by the system to
       create dialog boxes.
        Templates with a TMG extension are use for grabbing.
        Templates with a TMP extension are used for the generation phase.

   dBsee reads, by default, the data in this directory as a source for
   creating or generating projects. In case that a different source directory
   is to be used, dBsee can be taught to do so. The DBSEE.INI file, found
   in the \DBSEE4\BIN directory, contains a section entitled
   [environment]. Within this section, the dbtmp parameter indicates
   the source directory. By setting it to a new value, dBsee will use it
   automatically.

   --------------------------------------------------------------------------
   In order to use the new setting, the ";" character must be removed
   from the beginning of the line. Otherwise dBsee will treat the whole line
   as a comment.
   --------------------------------------------------------------------------

   The directory set by the dbtmp parameter must contain the three
   sub-directories CLIPPER5, BIN and EXE. These directories must contain
   the same files as the ones present in the sub-directories of TMP.

   A modification to one of the files in BIN or EXE will be reflected
   throughout every new project, while changing the CLIPPER5 files will
   influence every project under development.
    For this reason, it is advisable to make a copy of the directory
   structure, and assign the new directory's name to the dbtmp parameter.
   In this way, the default setup remains untouched, and eventual updates or
   upgrades will not overwrite the changes made.

Template in the development environment

   This solution is recommended when an application is developed for a client
   who asks for different standards.

   If changes to one or more templates are to be made, and these changes are
   only needed for a specific project but for all objects sharing the same
   templates, just copy the relative template files into the SOURCE or BIN
   sub-directory of the project and make the necessary changes. dBsee will
   automatically read these templates first.

Injection Points

   The intervention has effect only on the sources that have code entered
   into the injection points.

   The advantage of the last solution, in respect to an intervention at the
   Template level, is that the modifications are limited to the internal part
   of the object and in the point in which the modifications were made.
   Another object of the same type will not be influenced by this
   intervention.

   The insertion of source code in the injection points can be made within
   dBsee or outside it (directly within the source using any text editor).
   The process of Reverse Engineering, executed by dbUp, allows the
   programmer to bring the modifications into the source and make them
   permanent within the Repository.