Splitting a Database

[Guest]

Access 2003

I have been reading all of the threads on splitting a database and agree
that this is something that I need to do (multi users on a shared network
folder).

Here is my question. Our IT staff has configured Windows XP so that files
saved on the desktop or in my documents are actually being saved in a network
folder (not their local hard drive). In addition, users cannnot save to
their C: drive as this has been removed from their viewing.

What are the ramifications (if any) of users accessing the FE database on a
network folder?

Thanks for considering this.

 

[Douglas J. Steele]

Even if the front-end is on the server, having each user with his/her own
front-end is still going to help prevent many problems.

The downside of the front-end being on the server is that there will be more
network traffic than if it were on the hard drive. (In case your IT staff is
concerned, though, it shouldn't be more network traffic than if the
application isn't split, and everyone's using the same monolithic file on
the server)

 

[Guest]

I experienced exactly the same set-up in an authority where I worked once,
with each front end being in the user's 'home' folder on the network. While
not ideal it worked pretty well on the whole. Its certainly far better than
having all users using the same single file.

The one instance in which the network admin staff had to relax the policy
was when we tied in some databases to a GIS. The overheads of running that
completely over the wire were too great, and it was set up to download a
bunch of GIS files to the local machine when a user logged into the GIS
application.

Ken Sheridan
Stafford, England

 

[Tony Toews [MVP]]

Here is my question. Our IT staff has configured Windows XP so that files
saved on the desktop or in my documents are actually being saved in a network
folder (not their local hard drive). In addition, users cannnot save to
their C: drive as this has been removed from their viewing.

Yes, that works so long as they are not logging into the system via a
WAN. Performance would really suck and the risk of a corruption
would be quite high.

Mind you this problem would also exist if they were updating the FE
onto their own hard drive too.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm