>Hi,
>I am implementing my own audit log. I get the sample from UT magazine. And I would like to enhance it to allow rollback/rollforward.

A complete commercial auditing solution already exists - I think it is called FoxAudit.

I think that database servers also have auditing capacities, usually. You might consider it as an option.

On the other hand, if you want to create your own code (based on my article, I suppose), you will have to adapt it for rollback / roll forward. Specifically, you will have to separate information into different fields: old value, new value, data type, etc.

>
>I would like to get more details about it:
>If my application open multiple database, should each database has it own table for auditlog?

That is a possibility. Another is to keep it in a single table for all database. In this case, you would need an additional field to specify the database.

Personally, I would keep the separate databases in separate directories, and keep an audit table for each one.

>Does auditlog almost "same" with replication?

I don't understand the question. Can you say it in different words?