Websites that have databases behind them can, perhaps, be categorised into two groups. This division is pretty arbitrary, and there are lots of other ways that might be considered, but this is the one that is useful for showing where RekallWeb can be used.
Some websites, for instance Google or those used for online banking, may have truly enormous databases behind them, but the web interfaces are, from the user's point of view, essentially simple. Forms have only a few fields, and there is a fairly low level of interaction between fields in the form. The main Google search page is an example of this; there is a single test field, a couple of buttons, and a pair of radio buttons (OK, and some links, but these just go to other pages).
These sites also tend to have relatively sophisticated layouts, with lots of grapics and sundary stuff (actually, Google doesn't, but in that respect it is pretty unusual).
Other websites (and these are maybe more common in internal intranets) have forms that are very complex in terms of the fields and controls that are present, and in the interactions between them, but are rather simple in terms of layout and graphics. Typically, these are interfaces to databases that might otherwise have been implemented using a tool like Access (or, indeed, Rekall), but use the browser as a universal client. The advantage is centralised control, with all the following ease of update and rollout, but are significantly more difficult to implement.
It is this latter group that RekallWeb is aimed at. If you are looking to implement a replacement for something like PHPNuke, then RekallWeb is really not for you. But if you have an application that you might have used Access for, then Rekall and RekallWeb might be the way to go.
A First Example: The RekallRevealed Website