Problem with Replica

[Guest]

I have designed a secured database on my machine. I created a replica on a
shared network machine (used only to store the database replica.) I then
accessed the replica from a third machine but am having a problem - the user
can open the replica database and perform most functions - however one button
(which runs a macro) freezes access entirely and displays no error message!
(Other macros run without this problem.)

Even if i log onto the database as administrator on the third machine, the
same problem occurs.

However i can access the replica from my laptop and log on as either the
user or as administrator and everything works fine!!!!

I do not have a digital certicate in place. I have copied the workgroup
security file to the shared folder and joined that workgroup on both
machines. All machine are running Windows XP Pro and work on a workgroup
based network.

Any ideas? Thanks

 

[Joan Wild]

Why did you replicate the database? From your description, the users are on
a LAN - replication isn't needed. Furthermore, if you do replicate, you'd
only replicate the backend, since replication was meant for tables (data)
only.

If you don't really need replication, just split the database (do it
manually) and put the backend on the server along with the secure mdw.
Users will need modify permission on the folder where these files are
located. Give each user a copy of the frontend on their PC; also provide a
desktop shortcut with the following as the target:

"path to msaccess.exe" "path to frontend" /wrkgrp "path to secure mdw on
server"

No need to join the secure mdw using the workgroup administrator.

 

[Guest]

Thanks Joan - appreciate the advice - I used replication as i do a lot of
work (development and data work) on the database away from the office - its a
simple matter of returning to the office and synchronising so other users on
the LAN can use the updated database. Am i right in using replication in this
scenario.

 

[Joan Wild]

Yes that's fine for synchronizing data changes. However, from the sounds of
it you are replicating non-table objects. You don't want to do this. Only
replicate data.

You'd have a separate frontend to make design changes in. When you're ready
to deploy the updated frontend to users, you'd just overwrite their existing
frontend. For data changes, you can use replication.

 

[Guest]

Thanks again - i will test - just one question - when you say split manually
do you mean do not you the wizard - and if so, how do i split manually.
Many thanks

 

[Guest]

Joan - I have been puzzling over the solution - Please bear with me - i am a
layman!!

I have two requirements:
1. To be able to work on data whilst away from the office.
2. The project is an ongoing development and i will be making changes to
tables / adding etc.

As i understand it i will need to create a backend database on my machine
and replicate it on the server.
Then i will create 2 front ends - one that is linked to the replica on the
server - this is copied to other users and it is the one i use when updating
data at the office.
The second front end would be linked to the backend (design master) on my pc
and would allow me to work on data away from the office.

Am i on the right track?
If so how do i ensure the 2 front ends are synchronised?

Thanks

 

[David W. Fenton]

I have two requirements:
1. To be able to work on data whilst away from the office.
2. The project is an ongoing development and i will be making
changes to tables / adding etc.

As i understand it i will need to create a backend database on my
machine and replicate it on the server.
Then i will create 2 front ends - one that is linked to the
replica on the server - this is copied to other users and it is
the one i use when updating data at the office.
The second front end would be linked to the backend (design
master) on my pc and would allow me to work on data away from the
office.

Am i on the right track?

You're on the right track.

But *never* use your design master for production work. The DM is
first among equals of all the replicas -- it's the only one you can
make design changes in. If you're going to keep it on your laptop so
that you can make schema changes out of the office, make sure you
have a *different* replica that is the one you edit when you're just
doing data editing.

Otherwise, what you've outlined is correct.

 

[Guest]

Thanks David - appreciated!

You're on the right track.

But *never* use your design master for production work. The DM is
first among equals of all the replicas -- it's the only one you can
make design changes in. If you're going to keep it on your laptop so
that you can make schema changes out of the office, make sure you
have a *different* replica that is the one you edit when you're just
doing data editing.

Otherwise, what you've outlined is correct.