DBE

The DigaSQL.DLL can write the database information for each entry in database entry files. This is done when a new entry is created or an existing entry is updated. The DBE file will get the same filename as the media file (audio, text, etc.) but the extension ".DBE". If a database entry is deleted, the file is removed too. If you set this value to "WRITE" the DBE files are written, but they are never read (only backed up). The files are useful for the safety of your data, because you can use them to recover a crashed database server. The value "READWRITE" is needed if the database information is stored in DBE files on a changeable medium. Whenever a table is opened which has the readwrite-flag set, the table is emptied and rebuilt from the DBE files (in the audio directory on the medium). The user who wants to open such a table must have been granted the "Align" right. The value should be "READ" if the medium cannot be written (e.g. CD-ROM). If you have the keyword "READ" in this value you can also append the keyword "RECUR" (so that your entry appears "READ RECUR"). It means: not only the specified sound directory is read but all subdirectories are scanned for DBE files too. If you append the keyword "DRIVE" (e.g."READ DRIVE" ) it reads starting in the root of the drive where the sound directory is located. Also have a look on the values "Volatile" and "DefinitionSource" above, which are useful for the work with changeable media too. By default DBE files are neither written nor read.

Possible values: NO, FALSE, READ, WRITE, READWRITE, RECUR, DRIVE, READ RECUR, READ DRIVE, READWRITE DRIVE Default value: FALSE