> -----Original Message-----
> From: Lester Caine <lester@...>
> [mailto:lester@...]
> Sent: Tuesday, December 10, 2002 12:05 PM
> To: IBObjects@yahoogroups.com
> Subject: Re: [IBO] Multiple dbs and system wide unique keys
>

> No problem at all. Only the master database is used for that
> sort of problem. I don't actually use the information on the
> local copies, as all of the inserts and updates are
> broadcast from the main server, but I have a network request
> to get the next number from the master copies generator if
> an operator is trying to add a train from a remote location.
>

Ahh, so yours is mostly one way. The project I'm planning will initially
be 2-3 users at each of two separate sites, so a client/server setup at each
site
would be sufficient. However, the potential is there for a need to scale to
multiple offices
working with a central organizational wide database, at which time I would
need globally unique keys to be generated at any location with the data
propagated first to the central db but available for each office. Of
course, as
in your system, the propagation to the other offices would not be
time-critical,
but it would still have to be two-way.

I'll have to put together a prototype, I guess, with some actual
representative data
in order to test it out to see if it would hold up.

Anyone else's two-cents worth is still welcome!
Brian