Results 1 to 6 of 6
  1. #1
    ashu.doc is offline Competent Performer
    Windows XP Access 2003
    Join Date
    Jul 2012
    Posts
    124

    Re: spliting the database

    Hi
    I have around 10 forms, 20 tables, 6 macros, 4 queries in my database. How can I split my database, is there any specific pattern of putting the tables, forms etc in front/back end?


    Is the splitting only for the database which are on shared drive or also for the database which are distributable in multi-users which are not connected to each other in any way? my database will fall in second category.

  2. #2
    JoeM is offline VIP
    Windows XP Access 2007
    Join Date
    Jun 2012
    Posts
    3,904
    Typically, when you split a database, you put all the data tables in the back-end (and just the data tables).
    All other objects go in the front-end, and you usually distribute a front-end to each individual user (so they all have their own copy).

    Check out this article on splitting databases: http://office.microsoft.com/en-us/ac...010342026.aspx

  3. #3
    ashu.doc is offline Competent Performer
    Windows XP Access 2003
    Join Date
    Jul 2012
    Posts
    124
    Thats very helpful, I have splitted my database, but the front end DB still shows the table list, is that normal? So the users can still access tables? Or do I need to do something else to protect the FE DB tables?

  4. #4
    JoeM is offline VIP
    Windows XP Access 2007
    Join Date
    Jun 2012
    Posts
    3,904
    If split properly, you can view the Tables from the front-end, but they should all be linked tables (linked to the back-end database). They should have an arrow next to them indicating that they are linked tables.

    The only tables you might have on the front-end are temporary tables, or perhaps some sort of user specific table.

  5. #5
    ashu.doc is offline Competent Performer
    Windows XP Access 2003
    Join Date
    Jul 2012
    Posts
    124
    ok, so the reason for splitting the db and putting the tables in different file is that the .mdb file which users will have, they can't modify table design and relationships, and if I change the FE db into .MDE then even if they bypass startup options, then also they cant change the forms design. Am I correct?

  6. #6
    JoeM is offline VIP
    Windows XP Access 2007
    Join Date
    Jun 2012
    Posts
    3,904
    See here for reasons on why to split the access database:
    http://www.ehow.com/how_7587820_buil...ted-field.html
    http://www.techrepublic.com/blog/10t...-database/1119

    And here are reasons and details on why to create an MDE:
    http://www.databasedev.co.uk/microsoft-access-mde.html

    I think these should address most of your questions, and provide you with other good reasons to do this.
    It sounds like you are on the right track!

Please reply to this thread with any new information or opinions.

Similar Threads

  1. Replies: 5
    Last Post: 05-16-2012, 12:48 AM
  2. Replies: 20
    Last Post: 08-08-2011, 01:34 PM
  3. Replies: 3
    Last Post: 05-15-2011, 10:52 PM
  4. Replies: 1
    Last Post: 11-03-2010, 10:41 AM
  5. Spliting a form
    By Kimmy in forum Forms
    Replies: 1
    Last Post: 09-28-2010, 10:34 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Other Forums: Microsoft Office Forums