The Rekall Objects and Design Tables
Prev
Next

The Rekall Objects and Design Tables

Before going any further, two special tables that Rekall creates and uses should be mentioned. Rekall will attempt to create these when it access a server database and finds that they do not exist (subject to checking with you that they should be created). The first table, __RekallObjects, is used to store objects such as forms and reports when they are stored in a server database. The second table, __RekallDesign is used to store additional table-related information, such as validation expressions and Rekall-level default values [6].

Normally, you should allow Rekall to create these when it asks. One case that you might not want to do this is if you are using Rekall simply to look at (and maybe modify) data that is stored in existing tables, and where you will not be creating any forms or sthe like. In the event that Rekall cannot create the tables (maybe you have read-only access to the server database), it will warn you but continue [7].



[6] Rekall does not create the __RekallObjects table for the !Files entry, since in this case it does not store objects in the database.

[7] There is a minor irritation that Rekall will ask you each time you start. There should be an option to stop Rekall from bothering at all about these tables.

Prev
Next
Home