Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 2 of 2 total
Thread Keeping a carbon copy of tables
Tue, Aug 18 2009 1:52 AMPermanent Link

"John Postnikoff"
What is the best way to keep two DBISAM tables identical when any record is
changed, added or deleted?

Any tips are appreciated.

Tue, Aug 18 2009 3:50 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

John


Depends on a number of factors:

Fileserver or C/S?
Is it one way or two way synchronisation?
Which version of DBISAM?
Are both tables open simultaneously?
Are both tables being updated simultaneously?

If its one way with an older version of DBISAM I'd probably use the OnBefore/OnAfter events. With a newer version I'd write a custom engine function so I didn't have to worry about multiple instances of table components.

Two way as above but I'd use the events to write to a transaction log rather than direct to the other table and then have a batch job bringing in the feed from the other table.

If practicable I'd also consider a hardware solution


Roy Lambert [Team Elevate]
Image