backup differences between SE and OL - question.

In trying to decide the relative merits of each DB engine, I've come to a stumbling block in the backup section. OnLine is supposed to have a much better backup strategy in that we the system pukes, you can restore back to the very moment of the puke - and quick. That's cute, but I can't remember when I last ran into this situation - because I never have. What I have had happen is some idiot asking me to restore a row of a table which he updated accidentally. Or worse yet, in training a new programmer, having him do an unconstrained update which sets all of the rows instead of 1 row. In these cases I need to get the table back off yesterday's backup and get the data for that row or column out and merge it back into the table. I generally do this by getting the table.idx and table.dat files, creating a database, creating a table, point the tabname to the restored table name, get my data, do my updates, toast the database. Question: Can I do a similar thing if I cut over to Online? If so, how? Will I have to create an entirely new mirror database and restore from my archive into it? If so, that would require me to have twice the disk space and would be pretty time consuming. Is there a simpler way? - john (john%elsouth@concert.net)