Security and Replication

[Lavey]

Hi,

I have a split secured database, and need to share with colleagues in the states (am in the UK), I designed a lightweight frontend for the US users, but there was a huge lag problem as there is a lot of data being sent back an forth.

So... I replicated my back end file (secured) and placed on a local US server to overcome the need for excessive network traffic. The US guys have logged into the security file (.mdw is on a UK local server) but when they open the back end to synchronise they get a message 'cannot lock file'.

Is this because the secured back end is replicated and the .mdw is on UK server (altho the US users have joined this .mdw) ? or something else I have completley overlooked...

Look forward to hearing any1's thoughts on this..

 

[Lavey]

bump.....

 

[Newposter]

'cannot lock file' is not associated with the .mdw file, but rather it means that either the Access back end file is set for Windows permissions of Read-only (Access files *have* to have Write permissions), or the directory itself is not set to be writeable for them. Open up the Windows permission settings for the folder and file.
Another thing to look at is whether their copy of the Access program is set to Open Database Exclusively. This should be unchecked in the options so it can be opened in shared mode. Newposter
"Good judgment comes from experience. Experience comes from bad judgment."