Replication - Disable Conflict Viewer

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Anyway to prevent the conflict viewer from popping up. It doesn't happen
very often, but I don't want users to see it at all. As the administrator I
can clean it up, but it would be a lot easier if it took the most current
update rather than creating a conflict. Any help would be greatly
appreciated. Thanks.
 
Replication should only be used on the backend of a split database
application -- it is appropriate only for tables and queries, not for
forms, reports, etc. Your users should not be opening the backend
directly; they should be using the frontend of a split application.
The Conflict Viewer will not appear when opening the frontend.
 
Replication should only be used on the backend of a split database
application -- it is appropriate only for tables and queries, not
for forms, reports, etc. Your users should not be opening the
backend directly; they should be using the frontend of a split
application. The Conflict Viewer will not appear when opening the
frontend.
Click to expand...

This is exactly what I would have said.

I'd love it if you'd be willing to put some of your replication
knowledge and experience into my Jet Replication Wiki:

http://dfenton.com/DFA/Replication/

At the present time, I'm the only one who has added content. But
anyone who signs up and confirms their email can edit.
 
This is exactly what I would have said.

I'd love it if you'd be willing to put some of your replication
knowledge and experience into my Jet Replication Wiki:

http://dfenton.com/DFA/Replication/

At the present time, I'm the only one who has added content. But
anyone who signs up and confirms their email can edit.
Click to expand...


Well... I tried. Created an account and poked around to see if I could
make a small modification. Could not see how to modify the main page,
which is where I would have placed some additions:

What I was going to do was to put a top-level link to your page "What
not to believe in the Microsoft documentation." I think that page
deserves more prominence.

Another idea I had was to put a top-level page "Best practices". Could
be similar to the FAQ, but more directed. Two items I would add are:
- create the dropbox on the local machine (I got a hand-slapping once
from Michael Kaplan for creating the dropbox on a hub)
- split the application (with added emphasis about the perils of
replicating the frontend)



I had been meaning to contribute, but was reluctant to learn another
technology! This wiki is along the lines of a concept I would like to
see in *all* Microsoft software:
- a wiki (or similar) managed by MVP's
- or others meeting some community standard (Word, Excel, Access, etc)
- hosted on a MS-sponsored site
- referenced directly from the application Help menu

This concept is to handle what I see are a couple glaring weaknesses:
- users need a standard place to look for help
- that is dynamic
- and does not toe the company line
- but has a degree of credibility

So... can you open the main page, or add those links that I mentioned
above?
 
I need some advice. How can I create a replicant with all forms, etc. but
only replicated tables to the backend. If users are using the front end that
links to the be table, how are they supposed to work remotely (and use
replication)?
 
Well... I tried. Created an account and poked around to see if I
could make a small modification. Could not see how to modify the
main page, which is where I would have placed some additions:
Click to expand...

I don't allow anyone but me to alter the main page. All other pages
are editable.
What I was going to do was to put a top-level link to your page
"What not to believe in the Microsoft documentation." I think that
page deserves more prominence.
Click to expand...

Probably a good idea, yes.
Another idea I had was to put a top-level page "Best practices".
Could be similar to the FAQ, but more directed.
Click to expand...

Create a Best Practices article, and I'll link to it from the front
page.
Two items I would add are:
- create the dropbox on the local machine (I got a hand-slapping
once from Michael Kaplan for creating the dropbox on a hub)
Click to expand...

Many people seem to want to put the dropboxes all on the server.
I've never understood that one myself. Do you have MichKa's
explanation of why it's a bad idea to include?
- split the application (with added emphasis about the perils of
replicating the frontend)
Click to expand...

I've been intending to do that
I had been meaning to contribute, but was reluctant to learn
another technology!
Click to expand...

There's very little to learn for editing a Wiki, actually. I don't
think I've ever fixed the help links, though. If you go to
MediaWiki.org, you can read the help on how to edit. I guess I
should probably fix that!
This wiki is along the lines of a concept I would like to
see in *all* Microsoft software:
- a wiki (or similar) managed by MVP's
Click to expand...

I think Wikis are the way of the future. I think newsgroup FAQs
should all be maintained as Wikis.
- or others meeting some community standard (Word, Excel, Access,
etc) - hosted on a MS-sponsored site
- referenced directly from the application Help menu
Click to expand...

Unfortunately, MS has no Wiki technology on offer. It's Sharepoint
offerings don't come close to the elegance and ease of user of
Mediawiki, for instance.
This concept is to handle what I see are a couple glaring
weaknesses: - users need a standard place to look for help
- that is dynamic
- and does not toe the company line
- but has a degree of credibility
Click to expand...

I agree. that's why I started the Jet Replication Wiki, precisely
because I felt these lackes.
So... can you open the main page, or add those links that I
mentioned above?
Click to expand...

Create content, and I'll add it to the front page. I agree that the
front page needs to be revamped, but I just haven't gotten around to
it, partly because it felt lonely doing it all myself! :)

Let me know if you have problems. I should probably set up a
non-superuser logon to test editing capabilities. Or maybe I'll just
make you an editor, if you're interested in contributing
substantially.
 
I need some advice. How can I create a replicant with all forms,
etc. but only replicated tables to the backend. If users are
using the front end that links to the be table, how are they
supposed to work remotely (and use replication)?
Click to expand...

This is just the issue of relinking to the local back end. There is
code all over the place for this. Mine is here:

http://www.dfenton.com/DFA/download/Access/Reconnect.html

The main feature there is that it makes it easy to relink to
multiple back ends (which is not functionality that's needed in a
lot of applications).

Each user will get a copy of the front end, and the first time it's
opened, will be asked to point to the local back-end replica. That
would need to be done each time the front end is updated.

Of course, each user has her own copy of the front end. If you want
to be efficient, you'd reconnect to the back end before
distributing. The easiest way to do that is to make sure everyone
has the same path to their local replica, which is not really
possible when you're storing the front end in the user profile
(where it should be stored). However, since it's easy to figure out
the user profile location, you could have code that assumes the back
end is in the standard location under the particular user's profile,
and reconnect to that.

But that does require that the app be distributed with a standard
configuration, which may not have been in place before.

None of these issues are specific to replication. The issue of split
architecture (front end/back end) and how to distributed front end
updates and how to relink to the back end come up in the Access
newsgroups all the time. Scanning current posts in
microsoft.public.access and comp.databases.ms-access in Google
Groups should give you plenty of pointers to discusions of how to
resolve these issues.
 
You don't create a replica with all the forms. Instead, you create an
unreplicated frontend containing all the forms. Simply copy, email,
download, or whatever the new file to them. Since the frontend never
contains any data, there is no harm in your users simply replacing
their old frontend with the new one.

Tony Toews has a free system for automating the process of updating
the frontend on your users' computers.
http://www.granite.ab.ca/access/autofe.htm

If you haven't already done so, read Tony's advice about splitting the
database
http://www.granite.ab.ca/access/splitapp/index.htm
 
Back
Top