ODBC is a generic server database interface which connects to a range of server databases via ODBC drivers. Using the Rekall ODBC driver allows Rekall to connect to any server database for which here is an ODBC driver.
The ODBC interface allows Rekall to determine various information about the underlying server database, such as column types. However, it has a number of shortcomings, the major one of which is that it does not provide a means to identify a row that has just been inserted into the database. Because of this, the Rekall ODBC driver comprises a main driver plus helper modules for certain server databases; if the driver determines that the server database is one of these, then the corresponding helper module is used.
Currently, the driver has helper modules for MySQL and for Jet, which is the Microsoft Access database engine (for files with the .mdb extension). ( Since Rekall has its own MySQL driver, this is the recommended way to access a MySQL server database. )
The advanced settings for the server dialog are described below.
Map CR/LF in stringsIf set, the CR/LF (DOS/Windows style newline) character sequences in text data are mapped to LF when data is retrieved from the server database
Show system tablesBy default, the ODBC driver does not display tables which the underlying ODBC interface classifies as system tables. Setting this option will cause such tables to be listed.
Wrap names with [....]This option causes Rekall to wrap names in expressions with the [...] characters, hence the expression Client.ClientID = 12 becomes [Client].[ClientID] = 12. This notation, which is the same as used by Microsoft Access allows for names which contain the space character, and which sometimes appear as column names in XBase data files.