Should Replicaton Manager be installed on a server or a desktop?

[bberkow]

Should Replication Manager be installed on a server or a desktop?

And related: Does Synchronizer exit/close if you log off -- therefore do you
have to stay logged on to the computer on which Replication Manager is
running?

I had it running on a server and when I logged off I saw a message saying
"Closing Synchronizer". It strikes me as odd to have to stay logged on - but
perhaps I'm missing something.

We have a main office running an Access database that is connected via a
vpn to a smaller uptown office. I want to use Replication Manager to do an
indirect synch overnight.

Access 2002. Windows Server 2003. Windows XP desktops. Office Developer
XP/2002.

Thanks in advance.

[David W. Fenton]

=?Utf-8?B?YmJlcmtvdw==?= <bbe...@discussions.microsoft.com> wrote
in news:E49E4B22-CD1B-4907...@microsoft.com:

> Should Replication Manager be installed on a server or a desktop?

Neither. ReplMan is a waste of time, and you'll be better off moving
directly to programmatic control of replication.

> And related: Does Synchronizer exit/close if you log off --
> therefore do you have to stay logged on to the computer on which
> Replication Manager is running?

The synchronizer cannot be run as a system service and is always a
user-level process, so, yes, it has to run in an interactive logon.
But you can lock the workstation. A client of mine runs it on his
Small Business Server in one of the Terminal Server administrative
logons, and this works fine. But he did have to configure it so as
to not log off after inactivity (it just disconnects the remote
client, leaving the logon locked, which is fine).

> I had it running on a server and when I logged off I saw a message
> saying "Closing Synchronizer". It strikes me as odd to have to
> stay logged on - but perhaps I'm missing something.

This is because the synchronizer was not designed to run on a
server, which is something of an oversight, as it should have been.

None of that is ever going to change for Jet replication. Access
2010 with Sharepoint 2010 will offer a much easier approach to the
problem replication solves, and that's the direction I'm going to
recommend to my clients in the next few years, as they gradual
upgrade to A2010.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/