This is not really an answer to your question, but that's mainly because every time I have tried using recording-based test tools I have ended up either stuck and unable to make changes to the application, or spending a huge amount of time working around inflexibilities and assumptions to bring the recorded test into line with application changes.
These days I much prefer to use a fully scriptable approach. The project I am working for at the moment is getting a lot of value from
WATiR, a tool which drives Internet Explorer from scripts written in Ruby.
We have been able to hand over all the WATiR scripts to the test team and they are having fun extending and customising the test suite to reduce the amount of manual "grunt work" in testing web interfaces. Best of all, though is the way that when they needed to test the effect on the web screens of calls to our published web services it was really easy to add a few lines of Ruby to call the web services direct.
Ruby makes it just as easy to automate other integration test tasks such as setting database preconditions or sending JMS messages. I don't know of any "screen recording" test tool which comes anywhere close to being this useful.
