If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
MSAccess (2003) Splitting a Database is it just for LANs?
We have a database in our Parsippany, NJ office and need to have a user in
our Phildelphia office and Boston office update the database. Can we split the database and link the database to these two other locations? LaurieB. |
#2
|
|||
|
|||
MSAccess (2003) Splitting a Database is it just for LANs?
No, I would not advise that for 2 reasons:
1. A file server database running over a WAN is so slow as to be basically unusable. 2. The Internet often drops packets. For small files, it's not much of a problem. For large files like Access databases, it can easily lead to corruption. My suggestion is to use a thin client, like Terminal Services, or even RDP if there is only one person accessing at a time. That solves both problems. You still need to split the database, because 2 users should NEVER share a front-end. On a terminal server, just put a copy of the front-end in a folder for each user. -- Arvin Meyer, MCP, MVP http://www.datastrat.com http://www.accessmvp.com http://www.mvps.org/access "Laurie B." Laurie wrote in message ... We have a database in our Parsippany, NJ office and need to have a user in our Phildelphia office and Boston office update the database. Can we split the database and link the database to these two other locations? LaurieB. |
#3
|
|||
|
|||
MSAccess (2003) Splitting a Database is it just for LANs?
Arvin,
Thank you. I will have to open a service ticket with IT to discuss this with them. LaurieB. "Arvin Meyer [MVP]" wrote: No, I would not advise that for 2 reasons: 1. A file server database running over a WAN is so slow as to be basically unusable. 2. The Internet often drops packets. For small files, it's not much of a problem. For large files like Access databases, it can easily lead to corruption. My suggestion is to use a thin client, like Terminal Services, or even RDP if there is only one person accessing at a time. That solves both problems. You still need to split the database, because 2 users should NEVER share a front-end. On a terminal server, just put a copy of the front-end in a folder for each user. -- Arvin Meyer, MCP, MVP http://www.datastrat.com http://www.accessmvp.com http://www.mvps.org/access "Laurie B." Laurie wrote in message ... We have a database in our Parsippany, NJ office and need to have a user in our Phildelphia office and Boston office update the database. Can we split the database and link the database to these two other locations? LaurieB. . |
Thread Tools | |
Display Modes | |
|
|