A Microsoft Office (Excel, Word) forum. OfficeFrustration

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.

Go Back   Home » OfficeFrustration forum » Microsoft Access » General Discussion
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

MSAccess (2003) Splitting a Database is it just for LANs?



 
 
Thread Tools Display Modes
  #1  
Old May 17th, 2010, 03:50 AM posted to microsoft.public.access
Laurie B.
external usenet poster
 
Posts: 1
Default 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  
Old May 17th, 2010, 05:40 AM posted to microsoft.public.access
Arvin Meyer [MVP][_2_]
external usenet poster
 
Posts: 2,310
Default 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  
Old May 19th, 2010, 12:56 PM posted to microsoft.public.access
Laurie B.[_2_]
external usenet poster
 
Posts: 1
Default 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

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump


All times are GMT +1. The time now is 12:55 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 OfficeFrustration.
The comments are property of their posters.