For primary keys in distributed systems I recomend GUID's - they are guaranteed unique across all machines in the world until the year 3040, which makes a database merge almost (!) trivial. They are generated by an OS call in both Windows and UNIX systems. I typically store them in char(38). Check recent posts on this very topic for more ideas.

Any distributed app has to be fault tolerant and an efficient user of bandwidth. Interbase/Firebird provides all of the mechanisms for a fault tolerant system. I have seen allusions to compression mechanisms, but someone with more experience directly with Interbase/Firebird would probably have more specifics.

----- Original Message -----
From: frische_brise2003
To: firebird-support@yahoogroups.com
Sent: Monday, January 26, 2004 9:03 AM
Subject: [firebird-support] Replication


Hi all,

I'm writing an application which will be used by a company
to track data concerning product salse.
My app is used on both, desktops computers and laptops.
The salsemen are using their laptops disconnected from
the company's network, too. In this case, they get a own
copy of the database to work with.

Now, I'm planning to use IBReplicator to keep the databases
in sync.

My questions:
- has anybody already used IBReplicator and can tell me his
experience?
- on which topics do I have to keep keep an eye on when I
design my database (e.g. primary keys, generators....)?

Regards
Jürgen




------------------------------------------------------------------------------
Yahoo! Groups Links

a.. To visit your group on the web, go to:
http://groups.yahoo.com/group/firebird-support/

b.. To unsubscribe from this group, send an email to:
firebird-support-unsubscribe@yahoogroups.com

c.. Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.



[Non-text portions of this message have been removed]