?
Solved

MS Access Should I split my database?

Posted on 2013-01-10
5
Medium Priority
?
448 Views
Last Modified: 2013-01-10
I created a database that manages tasks/projects with report and query features.

The database will held on a network share with a max of 4 employee's connected at a given time.

Should I split it?

Any other advice to enhance integrity and avoid corruption?
0
Comment
Question by:DJPr0
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
5 Comments
 
LVL 61

Accepted Solution

by:
mbizup earned 2000 total points
ID: 38763427
-- >> Should I split it?

Yes.  Any shared database should be split with the users having individual copies of the UI (front-end) and the shared back-end data file residing on a server.

Take a look at this article for tips on avoiding corruption (and note that splitting your database is among those tips):
http://allenbrowne.com/ser-25.html
0
 
LVL 58
ID: 38763453
Absolutely and ditto everything else mbizup said.

Jim.
0
 
LVL 74

Expert Comment

by:Jeffrey Coachman
ID: 38763543
To be sure,
Splitting the database (for evenr *1* user) will always be a good idea.
See here too:
http://www.techrepublic.com/blog/10things/10-reasons-to-split-an-access-database/1119

And to be totally fair, ...yes , ...you can run an UNsplit DB if the number of users is low and the number of users in the DB at any one time will also be low (concurrency)...

*However* there will always exist the possibility of a crash that would not happen if the db was split.

When you Share one Access db file (for lack of a simpler explanation here), the user must pull down the entire app over the network.
This means that another use logging in may not have access to the db if something is open in design view.
It also means that you open yourself up to any number of the "Conflict" errors in Access.

But back to the "crash" scenario, with one user pulling the DB over the network.
Let's say another user logs into the database and is working.
Everything is fine, and neither user has any problems...
Sound great right...?
Sure, until one users machine goes wonky (crashes, Network hiccup, app lock up, Reboot while DB is open, unexpected "terminal" error, ...etc)
Now you have one machine where the DB is "Crashed", and the other where the db "appears" to be working fine.

Well, with one DB file being "shared", it won't be long before the "Good" database starts showing signs of corruption or worse...

Trust me, this all happened to me...
:-(

JeffCoachman
0
 
LVL 74

Expert Comment

by:Jeffrey Coachman
ID: 38763567
And to be fair here,...
I have posted a lot of info above.

But the bottom line is that mbizups post is the answer here.
   "Split the database"
So I do not want any points,...
(honest)
My info was just an illustration of what might happen if you don't split the db.
0
 

Author Closing Comment

by:DJPr0
ID: 38764127
Thanks!

Getting the ax out now.
0

Featured Post

Three Reasons Why Backup is Strategic

Backup is strategic to your business because your data is strategic to your business. Without backup, your business will fail. This white paper explains why it is vital for you to design and immediately execute a backup strategy to protect 100 percent of your data.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

It’s the first day of March, the weather is starting to warm up and the excitement of the upcoming St. Patrick’s Day holiday can be felt throughout the world.
In earlier versions of Windows (XP and before), you could drag a database to the taskbar, where it would appear as a taskbar icon to open that database.  This article shows how to recreate this functionality in Windows 7 through 10.
Using Microsoft Access, learn some simple rules for how to construct tables in a relational database. Split up all multi-value fields into single values: Split up fields that belong to other things into separate tables: Make sure that all record…
With Microsoft Access, learn how to specify relationships between tables and set various options on the relationship. Add the tables: Create the relationship: Decide if you’re going to set referential integrity: Decide if you want cascade upda…
Suggested Courses

765 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question