 |
|
 |
 |
| Rekall |
|
| Platform: x86 |
|
stock:
in stock |
ships in:
24 hrs. |
release date:
2002 |
|
|
list price:
$79.95 |
our price:
$63.95 |
you save:
20% |
![[order]](../pixelcentral/acc.order.gif) |
|
|
|
|
| status: |
current |
|
| version: |
1 |
|
| format: |
CD-ROM |
|
| packaging: |
DVD style plastic case |
|
| license: |
Single License |
|
| related links |
|
Rekall is a database front-end. It is not itself a database -- data is stored somewhere else, in an SQL server, and Rekall is fundementaly just a tool to extract, display and update that data (of course, it does lots more than that, it does forms and reports and scripting and so on). It is database agnostic, and does not have any preferred database in the sense that Access® uses the Jet® database engine. |
|
 |
|
|
|
|
|
|
 |
Rekall can do all the things that you would expect of a database front-end (or if it can\'t, let us know!). You can design and use forms and reports, construct database queries, and import and export data (actually, you can copy data -- import is just copy file to table, and export is just copy table to file).
Rekall can be scripted using the the Python language. You can arrange that a script is executed when various events occur (for instance, when the user changes the value of a control). Scripts can be associated directly with the event, but you can also store scripts in script modules for more general use.
And, of course, you have full access to all the modules that are available for Python. Plus, Rekall has an integrated Python debugger, and uses the Scintilla editor to support syntax highlighting.
|
 |
|
|
|
|
|
| |
 |
 |
|
| | Currently, Rekall supports the following database formats:
| | • | MySQL
| | • | PostgreSQL
| | • | XBase with XBSQL (an SQL wrapper library for the XBase access library)
| | These will be expanded later, particularly once Rekall moves over to QTSQL in Qt3.
|
|
|
![[view your shopping cart]](../pixelcentral/acc.tuxcart.gif)
