Merging databases

[louishong]

Not sure what happened to yesterday's post. It seems to have
disappeared! Here's the issue:

We currently run an Access application in the West Coast for tracking
resource centric data. For those located in the West the program zips
along fine but the folks in the East Coast are having a nightmarish
performance issue.

We've had our tech guys take a look and it's due to the network speed
across a long distance and there's nothing much that can be done.
We've minimized the number of hops and we're practically on the network
backbone.

What were planning to do is create a copy on another server on the East
Coast. Doing this poses a serious problem for us. All the tables have
auto ID enabled so if records are created on both machines trying to
merge them just won't be possible due to conflicting IDs since the auto
ID will sequentially select the next numeric value.

We can't create a replicated version as we'll have the same network
performance issue. Has anyone found a solution or a workaround for
this problem?

[Larry Linson]

There are a number of approaches you could use.

One that is simple and relatively inexpensive (because it will not require a
rewrite of your application) is to use Windows Terminal Services to allow
the remote users to actually run on the server. That's been discussed a
great deal here, and in the microsoft.public.access newsgroup -- to find
those discussions, search the archives at http://groups.google.com. Many of
the discussions also will include links to websites where there is
additional information.

Larry Linson
Microsoft Access MVP

<lo*******@lycos.comwrote in message
news:11*********************@i39g2000hsf.googlegro ups.com...

Not sure what happened to yesterday's post. It seems to have
disappeared! Here's the issue:

We currently run an Access application in the West Coast for tracking
resource centric data. For those located in the West the program zips
along fine but the folks in the East Coast are having a nightmarish
performance issue.

We've had our tech guys take a look and it's due to the network speed
across a long distance and there's nothing much that can be done.
We've minimized the number of hops and we're practically on the network
backbone.

What were planning to do is create a copy on another server on the East
Coast. Doing this poses a serious problem for us. All the tables have
auto ID enabled so if records are created on both machines trying to
merge them just won't be possible due to conflicting IDs since the auto
ID will sequentially select the next numeric value.

We can't create a replicated version as we'll have the same network
performance issue. Has anyone found a solution or a workaround for
this problem?