Tim,

First of all I would not want to drag you into this any deeper than it is required to
answer  the ElevateDB related questions. And I think we are probably through with that. So
you should probably skip the rest of the post, unless you are realy-realy bored.  

<<Yes, but is the issue whether the main office needs to see the data in a
specific sort order or use a specific collation for comparisons.  This is a
separate issue from what the display of the data looks like or whether they
can read it.  The collation only affects the sort order and comparisons.  If
that isn't an issue, then using the UNI collation will work fine for the
main office.>>

The sort order is the main concern here. People want to see the same data  sorted as it is
comfortable for them.


<<
<< This is something I  cannot avoid.  The local offices must have their
database localized, and the central office must have all the data from the
different countries.  >>

That's not what I was referring to.  What I was referring to was trying to
have multiple versions of the database for each collation at the central
office.
>>

Yes, I that's the way I understood it. But since the database needs to be localized
anyway, keeping a copy of all localizations on the main office  server and setting up the
network to replicate the changes for all of them, should not require much time from me.
Though it would significantly increase the load of the server.  Or am I wrong here?

Regards,
Leslie

Leslie


A few questions:

Does the central office only read the data or does it alter any of it as well?

Is the data needed with the information from all the offices merged or is it handled on an office by office basis?

Roy Lambert [Team Elevate]

Leslie,

<< First of all I would not want to drag you into this any deeper than it is
required to answer  the ElevateDB related questions. And I think we are
probably through with that. So you should probably skip the rest of the
post, unless you are realy-realy bored.  >>

Well, I always finish what I start, so.....

<< The sort order is the main concern here. People want to see the same data
sorted as it is comfortable for them.  >>

Okay, in that case you will need separate collations.

<< Yes, I that's the way I understood it. But since the database needs to be
localized anyway, keeping a copy of all localizations on the main office
server and setting up the network to replicate the changes for all of them,
should not require much time from me. Though it would significantly increase
the load of the server.  Or am I wrong here? >>

I doubt that it would increase the load on the server that much, and there
are ways to off-load the processing of the actual replication to another
machine if there are any load issues.  The main issue is simply making sure
that everything stays in sync properly.

--
Tim Young
Elevate Software
www.elevatesoft.com