Re: 4 Synch Questions
- From: "David W. Fenton" <dXXXfenton@xxxxxxxxxxxxxxxx>
- Date: Sat, 22 Oct 2005 14:09:09 -0500
"=?Utf-8?B?TmlnZWwgU2NvdHQ=?=" <nigel(removethisbit)@amscott.com(and
this.net)> wrote in
news:E94ED64A-3EE8-4268-AF39-A312007D1E06@xxxxxxxxxxxxx:
> I can't find answers to the following and would really appreciate
> a bit of help:
>
> 1 If you use ReplMan to set up an automatic Synchronizer schedule
> running every 15 minutes will the Microsoft Conflict Viewer keep
> popping up also every 15 minutes if there are conflicts, or is
> there some way to disable the Conflict Viewer (so I could deal
> with any conflicts in code)?
The conlfict viewer wizard runs only when you open a replica in the
Access UI that has conflict tables in it.
But you should be checking for conflicts and notifying someone that
they need to be resolved.
I would also question the utility of a 15-minute synch schedule.
Sounds like you really want real-time data, and that's not possible.
> 2 When the Synchronizer is automatically scheduled (Windows XP
> and Access 2003 on the local pcs) will the Synchronizer always
> appear on the Taskbar?
Yes. So far as I know there's no way to hide it. This is by design,
I think.
> 3 Does MichKa's TSI Synchronizer replace ReplMan but not the
> Synchronizer (ie do you still need to install the Access
> Synchronizer on the local pcs as well as TSI Synchronizer)?
You can use the TSI Synchronizer to do programatically a lot of the
things that ReplMan provides a UI for. The TSI Synchronizer also
does some other things.
You might also examine JRO, as it includes much of the functionality
in the TSI Synchronizer (though not al of it).
> 4 With Access 2003 can you still not use DAO to programatically
> perform an Indirect synch (since JRO is being deprecated)?
DAO has not being enhanced since the introduction of Access 2000. I
don't know what will happen with Access 12 -- replication may be
dropped entirely in favor of something implemented with SharePoint.
Microsoft is extremely confused (to put it politely) in their
strategy for supporting Jet replication. They are no longer
including ReplMan in the Visual Studio version that replaces the
Office Developer version, but they are then deprecating the only
technology that allows you to programatically control replication
fully (i.e., JRO). You'd think that MS wants to kill off replication
in Jet, if it were not for the fact that they are just as confused
about ADO, which they are no longer pushing as the default interface
for Jet data -- classic ADO is just as dead as DAO, because all
development has moved to ADO.NET, which is not at all the same
thing, and can't be used in Access.
--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc
.
- Follow-Ups:
- Re: 4 Synch Questions
- From: Nigel Scott
- Re: 4 Synch Questions
- Prev by Date: Re: TSI Un-replicator not working ?
- Next by Date: Re: 4 Synch Questions
- Previous by thread: TSI Un-replicator not working ?
- Next by thread: Re: 4 Synch Questions
- Index(es):
Relevant Pages
|
