replication problems

[Guest]

I am trying to replicate a database I created onto our network so it can be
access by another person mostly for data entry. When I set up the
replication, I cannot open the forms from the switchboard. Also, When I went
to check on the security settings, it is stuck at the default user admin and
not the one I created for the other person to use. Is there something that I
am missing? I hope I explained my question so that I can be advised on what
to do. Thanks

 

[Joan Wild]

Replication is meant only for data (i.e. tables), not for any other objects.
You should have split your mdb and only replicated the backend.

If you and the other person are on the same LAN, there really is no need for
replication. Replication would be used by someone who isn't connected to
the server (on the road), but they'd still be able to make changes and have
them synchronized when they return to the office.

In your case, it sounds like you'd just need to put the backend on the
server, and give each user a copy of the frontend.

 

[Guest]

Thanks for responding. When I created the database,it was not on the network.
Should I just move the whole file to the network so that it can be
accessible? Secondly, if I move it to the network, will I be able to setup
different access accounts? Thirdly, does the second computer that will access
the database have the same version of Access?

 

[Joan Wild]

First you will need to synchronize the replicas you have to the master.
Then unreplicate the database.

Once it's unreplicated, split it using Tools, database utilities, database
splitter. This will split the mdb into two files - a backend (which
contains just the tables/relationship) and a frontend( contains all other
objects). The frontend would contain links to the tables in the backend.

You would put the backend in a folder on the server (the splitter wizard
will prompt you for a location for the backend). Ensure the windows
permissions on this folder are set to read/write/create/delete for all users
that will use the database.

Give a copy of the frontend to each user. This frontend mdb would be placed
somewhere on their PC.

That should be sufficient to get multiple users working with the database.

Regarding access, you can implement user level security. It is a bit of a
learning curve, so study up on it, and practice on a copy of your mdb.

Security FAQ
http://support.microsoft.com/?id=207793

Security Whitepaper
http://support.microsoft.com/?id=148555

I've also outlined the detailed steps at
www.jmwild.com/AccessSecurity.htm

As for differing versions of Access, the easiest is to leave everything in
the lowest version (I'm assuming all computers have at least version 2000 -
post back if not).

Version 2002, 2003 can read version 2000 without a problem.

 

[Guest]

I will let you know how it comes out. Thanks for your help.

 

[Guest]

Ms. Wild,

I see that you are knowledgable in replication and probably synchronization.

At the end of each day, I synchronize the replicas with the Design Master.
On the 17th, for some reason, I can see the data in their replicas and
although the synch process tells me that it was successfull, the data from
the 17th is not there. I can't figure out why.

They are offsite and they copy their database to the server. Then they pull
down the updated version to their desktops to continue working in. That part
is especially important as it allows the manager to monitor the site visit
and prepare reports if needed.

Hope you can help.

 

[Joan Wild]

You really should ask in the replication group. I can tell you that copying
a replicated database is a no-no. It defeats the purpose of replicating.
They should be connecting, and then synchronizing. But you'll get more
clarification in the replication newsgroup.

 

[David W. Fenton]

At the end of each day, I synchronize the replicas with the Design
Master. On the 17th, for some reason, I can see the data in their
replicas and although the synch process tells me that it was
successfull, the data from the 17th is not there. I can't figure
out why.

They are offsite and they copy their database to the server. Then
they pull down the updated version to their desktops to continue
working in. That part is especially important as it allows the
manager to monitor the site visit and prepare reports if needed.

As Joan recommends, you're likely to get more specific help in the
Jet Replication newsgroup (microsoft.public.access.replication).
There are a handful of us there who try to answer all questions.

As Joan says, copying and moving replicas is a bad thing to do, as
it breaks the basic structure of replication, and can eventually
lead to corruption of the data and even complete loss of the whole
database.

You seem to be in the early stages of corruption, when you can't
rely on the synch to make all replicas identical. This happens when
you copy and move replicas because you end up creating what we call
"dead replicas." An explanation of what a "dead replica" is and why
they happen and what problems they cause can be found here
(unwrapped, all on one line):

http://groups.google.com/group/comp.databases.ms-access/msg/9f5a84194
fa6c653

It's possible to recover from these problems, but it's better to
avoid them in the first place.