Erik,

>If you are storing data in an alternate location for crash recovery, I think that qualifies as replication, no?

I was refering to storing particular data in particular production tables which provides extra information when things go wrong. For example: I've had trouble with a client saying that the program didn't calculate the stock right. I've implemented a stock counter for each mutation that takes place. Thefore I'm able to track the stock trough time, but it also enables me to check if this value matches the stock field in the articles table. Besides stock information I hold some other information in other places. Once when the articles table crashed beyond repair, I was able to reconstruct the table by all information scattered troughout the system. I was able to do this because I denormalized tables. mostly for performance reasons but also for recovery purposes.

Within DB world, replication is either based on whole tables (snapshot copies) or on the transaction log. Since we don't have a native transaction log within VFP, most replication of whole tables is the most easy thing to do.

Walter,