Results 1 to 6 of 6
  1. #1
    Join Date
    Nov 2006
    Posts
    43

    Unanswered: Pros and Cons about splitting a database

    Hello everyone, Im looking for a list of Pros and Cons about splitting a database. Does anyone have one or able to put one together for me? We are using MS Access 2003

    Thanks

  2. #2
    Join Date
    Jun 2005
    Location
    Richmond, Virginia USA
    Posts
    2,763
    Provided Answers: 19
    If this is a multi-user database, there is no 'Con' position! Running a multi-user database without each user having a copy of the front end on their machine is a tried and true method of creating all kinds of problems, involving timing, tables being locked and last, but certainly not least, major data corruption!

    You'll see reports of some users having had multi-user, non-split DBs running successfully for a period time, but this is totally meaningless! I've seen reports of such apps running smoothly for months, even years (14 years being the longest!) and then bombing out! And once trouble starts it never stops! All it apparently takes is some combination of events to occur and BOOM!

    It's not a question of will the non-split app become corrupt, but rather of when will it become corrupt. And once this type of corruption starts it will occur over and over and over again, until the app is split!

    Linq ;0)>
    Hope this helps!

    The problem with making anything foolproof...is that fools are so darn ingenious!

    All posts/responses based on Access 2003/2007

  3. #3
    Join Date
    Nov 2006
    Posts
    43
    Thanks Linq, definitely going to split

  4. #4
    Join Date
    Apr 2011
    Posts
    2

    how do you split off the front end forms

    how do you split off the front end forms and leave the main tables on a server

  5. #5
    Join Date
    Jun 2005
    Location
    Richmond, Virginia USA
    Posts
    2,763
    Provided Answers: 19
    1. Make a back up copy of your database and keep it in a secure location!
    2. Compile your file and make any needed corrections.
    3. To split the file go to Tools - Database Utilities - Database Splitter
    4. Place the back end file on the server
    5. To link the front end to the back end, from the front end file go to File - Get External Data - Link Tables and navigate to the back end on the server.
    Hope this helps!

    The problem with making anything foolproof...is that fools are so darn ingenious!

    All posts/responses based on Access 2003/2007

  6. #6
    Join Date
    Feb 2004
    Location
    New Zealand
    Posts
    1,418
    Provided Answers: 7
    What a do
    Is create folder on the server then share it as a hidden shear ie data$
    then move the database there
    Then relink the table but point them to \\server name\data$\data.mdb
    The reason for this it not map to a map drive there for the user can't delete what they cant see lol
    hope this help

    See clear as mud


    StePhan McKillen
    the aim is store once, not store multiple times
    Remember... Optimize 'til you die!
    Progaming environment:
    Access based on my own environment: DAO3.6/A97/A2000/A2003/A2007/A2010
    VB based on my own environment: vb6 sp5
    ASP based on my own environment: 5.6
    VB-NET based on my own environment started 2007
    SQL-2005 based on my own environment started 2008
    MYLE
    YOUR PASSWORD IS JUST LIKE YOUR TOOTHBRUSH DON'T SHARE IT.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •