Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Sharing Microsoft Access Database

Status
Not open for further replies.

ajg001

MIS
Joined
Apr 26, 2000
Messages
2
Location
US
I have three separate plants that want to access the same access database and make changes to records.&nbsp;&nbsp;What options do I have in order to make this work the best?&nbsp;&nbsp;Is replication the answer, there could be at times when people have the same file open.<br><br><br>Thanks<br>Angie<br><A HREF="mailto:Angie.Gode@auimail.com">Angie.Gode@auimail.com</A>
 
All you really need to do is put the database in a shared network location and give them rights to access it. Several people can use an Access database at the same time. In fact, two people can be editing the same record at the same time. Of course if you fear that might happen then there are steps you can take to prevent it. <br><br>The simplest way to make sure they are not editing the same record is to go to Tools, Options and choose the Advanced tab. Set the Default Record Locking to Edited Record.<br><br>This is the simple answer but it may be all you need. If you have other concerns we can address them.
 
This isn't really desirable as we do not have a T1 connection between plants, so accessing the database will be slow.&nbsp;&nbsp;Any other suggestions?
 
Replication may be the answer for you then. However if this is a mission-critical database it could be justifiable to run the T1. Especially if it will be heavily used and up to date information is essential.&nbsp;&nbsp;Good luck.
 
Upfront I'd like to say I've never used replication. However in case you're interested I did just read an article on replication that suggested &quot;partial&quot; replication might be faster and preferable in some instances, such as if all 3 plants are not using the same records. There's more info at:<br><A HREF=" TARGET="_new">
 
My company attempted to use a replicated database. This worked fine until we expanded our network. The new phase of our building is on a different sub-net and Access started confusing its indexes and attempted to write different records to the same location. I'm not sure if partial replication would solve this problem. <p>Colin Chevrier<br><a href=mailto:colin.chevrier@ca.jdsunph.com>colin.chevrier@ca.jdsunph.com</a><br><a href= > </a><br>
 
On a shared Access database on a network, the &quot;Default Record Locking&quot; option will not stay with &quot;Edited Records&quot; and defaults back to &quot;No Locks&quot; after several users work in it (not sure exactly when this takes place).

I've turned to setting this option on the forms, but would like to understand what is going on. We do have somewhat frequent corruption of databases.
 
Do you back up and compact nightly? This solved all my corrusption problems.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top