|
|
|||||||||
|
|||||||||
|
|||||||||
| |
|||
| ||||||||||||||||||||||||||
![]() |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Display Modes |
|
#1
|
|||
|
|||
|
Access database, server and local copy
Hi,
I've built an application that uses an access database. I would like to have a central copy of this database on a work server and allow access for several employees. We are field based - so we would need to keep a local copy on our laptops and then update the master database (probably daily). Can i do this with replication? Do i need the server with the master copy to have database server software? What would be the easiest (and cheapest) way to do this? Thanks for looking |
|
#2
|
|||
|
|||
|
Hello,
It looks like you need to split the DB and put the backend on the server. The front end can then be put on any other desktop or laptop and access the table (backend) when you establish the link between the two. If the server is on your network then this can be done. Just follow the server route to the backend of the access DB and voila, you can access then DB from the LT or PC MCB |
|
#3
|
|||
|
|||
|
"Splitting my database?!" - Sounds rather painful!
I've found a few web sites to read - so that's me hitting the books for a while. Thanks very much for the reply! |
|
#4
|
||||
|
||||
|
Splitting the database will only work for you if your people can connect to the server while in the field.
If this is not the case, then you are correct about needing to do some sort of daily update. You will have to create some sort of merge for the local data to the master data. How automated or manual this process is, depends a lot on your environment and business processes.
__________________
P.S. I am looking for work. <grin>. |
![]() |
| Viewing: Dev Articles Community Forums > Databases > Microsoft Access Development > Access database, server and local copy |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
|
|