Deutsch English
Alphabetical index
Array functions
CGI functions
Data types
Date functions
Debugging
Fulltext functions
Language elements
Numerical functions
Operators
Other functions
Ramtext functions
Selecting
Socket functions
Statistical functions
Stream functions
String functions
System functions
Table functions
  • access()
  • andmarks()
  • autofield()
  • autorecno()
  • blobsize()
  • blobtype()
  • cleardat()
  • closedb()
  • copyblob()
  • copymemo()
  • dbdir()
  • dbname()
  • dbno()
  • dbrights()
  • deldb()
  • delindex()
  • delmark()
  • delmarkedrecords()
  • delmarks()
  • delrec()
  • editoff()
  • editon()
  • embedblob()
  • exists()
  • fields()
  • filemode()
  • fileno()
  • filesize()
  • findandmark()
  • findauto()
  • findrec()
  • firstmark()
  • firstrec()
  • flushdb()
  • fsum()
  • genindex()
  • getcode()
  • getdef()
  • getfield()
  • getmarks()
  • getmode()
  • getpw()
  • getrec()
  • getrfield()
  • getstructure()
  • gettype()
  • incrfield()
  • inddef()
  • indname()
  • indno()
  • ismark()
  • label()
  • labelno()
  • lastrec()
  • link()
  • linkblob()
  • linkinfo()
  • lock()
  • makedb()
  • markdoubles()
  • markindex()
  • markpattern()
  • maxfile()
  • maxlabel()
  • memolen()
  • memostr()
  • newtable()
  • nextmark()
  • nextrec()
  • nmarks()
  • opendb()
  • prevrec()
  • primfile()
  • primtable()
  • putmarks()
  • putrec()
  • readmemo()
  • readrec()
  • recno()
  • recno()
  • recnr()
  • regenall()
  • regenind()
  • relation()
  • rendb()
  • reopendb()
  • revmarks()
  • setalias()
  • setauto()
  • setfield()
  • setfields()
  • setfilter()
  • setmark()
  • setmarks()
  • setrecord()
  • setrfield()
  • sortmark()
  • treeinfo()
  • unlock()
  • writerec()
    Text functions
    Home    Overview    Search    Impressum    Contact    Members
    Topic complex Table functions
    Function makedb()
    Short Creates a new table
    Syntax MAKEDB(db_p, db_pw : STRING; c : INTEGER; def : STRING[; db_i : INTEGER]) : INTEGER
    Parameter db_p : path to the main file (.dat) of the table
    db_pw : password of the table
    db_c : scrambling code of the table
    def : path to a structure definition
    db_i : path to a import table
    Return 0 : table successfully created
    else : error code
    See also:
    genrel() genlist()
    Description The structure definition is the name of a text file which is structured like this:

    [STRUCTURE]
    field_1=fieldspec
    field_2=fieldspec
    ...
    [INDEX]
    id=indexdef
    index_1=ind-name:ind-desc
    index_2=ind-name:ind-desc
    ...

    The section below [INDEX] is only necessary if the table is numerated automatically.

    A field specification fieldspec has the following structure:

    field_identifier, type_definition[,(import_field)]

    All identifiers are valid for a field identifier which start with a letter or a undeline and include only letters, figures and underlines. The maximum length is 35 chars.

    The following type definitions are valid:

    STRINGS:

    STRING,length (length from 1 to 255)
    -> string field with the defined maximum length

    NUMBERS:

    NUMBER,NumCode[,decimal places][,U]
    -> numeric field depending on NumCode
    NumCode type            value facet
     1      Byte            whole numbers from 0 to 255
     2      16-Bit-Integer  whole numbers from - 32768 to + 32767
     4*     32-Bit Integer  whole numbers from - 2147483648 to + 2147483647
     6**    6-Byte REAL     floating-point number (old Borland format)
                            from -2.9 x 10^39 to +1.7 x 10^38 and 11-12 sign. digits
     8***   8-Byte-REAL     floating point number (ANSI double)
                            from -5.0 x 10^324 to +1.7 x 10^308 and 15-16 sign. digits

    *) only tdbengine, incompatible to VDP or TurboDatenbank
    **) compatible to all VDP and TurboDatenbank versions
    ***) only tdbengine and VDP (since 2.5)

    Decimal places are considered only at the REAL types. They are integral for the data transfer with the functions GetField and SetField as well as at the export to other database formats. Internal all REAL types are saved allways with the best accuracy.

    Is the parameter U defined in selections tdbengine differs between the value 0 and "undefined".

    Memos and Blobs:

    MEMO
    -> makes a memo field

    The content of a memo field is a link to a additional memo file. In memo files only unformated textes are saved.

    BLOB [,blocksize]
    -> makes a blob field

    The content of a blob field is a link to an additional blob file. In blob files any data is saved. With blocksize you can define the size of the clusters in the blob file (Minimum = 64, Maximum = 8192, Default = 4096). Per entry to a blob file an half cluster is lost in avarage, but to small clusters extend the access time.

    AUTO-INCREMENT:

    AUTO[,start number]
    -> auto number field (AUTO INCREMENT)

    The counting starts (in a new table) with a start number (resp. 1 if no one is specified)

    Date and time:

    DATE
    -> Date field (dd.mm.yyyy)

    TIME
    -> Time field (hh:mm)

    Listing:

    SELECT,value1,value2,value3,...
    -> select field with the defined value facet

    Links:

    REL
    -> relations field between the specified tables

    Attention: tdbengine does not create the belonging relations table. Therefor is the function GenRel.

    LINK,Table
    -> ADL-Link field to the specified table

    It is not checked if the table exists or if it is numerated automatically.

    Define import fields:

    If in GenTable a source is specified, the specified field is replaced by the content of the defined import field of the source.
    If no import field is defined the specified field name is used.

    If the same filename is specified as source and target, the table is restructered accordant. To use an abbreviation for the same file name you can use "@".

    Note: The structure definition is rather a maschine file which is created by a utility programm by interaction with the user. If you want to create a structure definition manually you should attend to the following necesarilly:

    * The numbering of the fields has to be complete.
    * No field number may occur twice.
    * Add new fields always at the end, because the order is not essential.
    * If you want to change a field identifier in course of a restructuring, do not forget to define the previous identifier as a import field. Otherwise the content of the field is lost.

    The restructuring of a table is always a critical event if the table already contains information. You can be conducive to more data security by not using direct restructuring. Instead of that rename the table with RenTable define the renamed table as source. If an error occurs you can still access to the previous table.

    User comments:
    Write a comment:
    Name
    EMail
    Subject
    Text (Switch mode)

    Choose between
    the normal and the
    advanced editor.
    The advanced editor
    runs in IE 5+ and
    Mozilla 1.4+ only
    SPAM-Protection Please enter tdbengine in this field.

    tdbengine chat
    irc.tdbengine.org
    #tdbengine

       Copyright © 2003-2004 tdb Software Service GmbH
       Alle rechte vorbehalten. / All rights reserved
       Last changed: 21.10.2004
    {Fehler für :execmacro{execmacro="sessionspy"}