Results 1 to 2 of 2
  1. #1
    Join Date
    Oct 2003
    Posts
    81

    Lightbulb Unanswered: Database splitting - more than one data file

    I currently have a database which is split into a front end mde application and a back end mdb data file. Recent events and corruptions have prompted me to consider splitting the back end database further. i.e. A data file for each main section (around 4-5).

    Can this be done? If so, what things do I need to consider and is this a wise decision?

    Additional Information
    ---------------------

    I have a setup of around 30 users. 15 connected through Terminal Services and 15 standalone PC's running a copy of access runtime. Runtime doesn't allow me to go into linked table manager so I would need a way around that.

    Any advice or comments are welcome. Thanks in advance.

  2. #2
    Join Date
    Feb 2004
    Location
    New Zealand
    Posts
    1,422
    Provided Answers: 7
    Yes it can be done

    What I did was

    Have is a Event Report System Link to

    a Event Data Backend , Hazard Management Backend,Training Data Backend

    Also each one have there own frount end Linking to each other

    There about 6 year work There it groven over the Years
    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
  •