Results 1 to 3 of 3
  1. #1
    marinelizard is offline Novice
    Windows 7 64bit Access 2013
    Join Date
    Dec 2015
    Posts
    2

    Clarification about splitting a database: what can and can't FE users change?

    I'm preparing to split a database accessed by several users on a network. After perusing several excellent threads about splitting a database and using the front-end and back-end, I'm confused on what can and can't be manipulated in local FE by users. Some threads indicate that FE users will not be able to create their own queries, just use forms to input data or create reports. Other threads indicate that the BE protects the data in the tables and that each user with their local copy can create their own queries, etc.

    I would like my users to be able to create their own queries since they often have last-minute tasks requiring them to extract data from tables, but I would like to keep the data safe in a back-end, accessed only by me. How do I achieve this goal (specific steps or things to keep or not keep in FE, BE, respectively)?

    I've also seen threads that provide vb script that will launch the FE database each time, making changes to the FE easy to manage.

    https://www.accessforums.net/code-re...life-7572.html



    Can I keep the flexibility I described above while also maintaining something like a script-launched FE?

  2. #2
    June7's Avatar
    June7 is online now VIP
    Windows 7 64bit Access 2010 32bit
    Join Date
    May 2011
    Location
    The Great Land
    Posts
    53,603
    You can allow users to create queries in the frontend but since every user should have their own copy of frontend on their local workstation, every time you distribute a new version of the frontend, their personalized work will be lost.
    How to attach file: http://www.accessforums.net/showthread.php?t=70301 To provide db: copy, remove confidential data, run compact & repair, zip w/Windows Compression.

  3. #3
    CJ_London is offline VIP
    Windows 8 Access 2010 32bit
    Join Date
    Mar 2015
    Posts
    11,831
    I
    would like my users to be able to create their own queries since they often have last-minute tasks requiring them to extract data from tables,
    but I would like to keep the data safe in a back-end, accessed only by me
    these two requirements are incompatible. If you allow users to write queries, they can write queries to change/add/delete data. Assuming you are linking, they can also open the linked table and change data that way as well. What will be protected is your table design.
    Some threads indicate that FE users will not be able to create their own queries
    they can if you let them
    , just use forms to input data or create reports.
    this is what is recommended

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

Similar Threads

  1. Force Password Change for Db Users
    By Blindability in forum Access
    Replies: 1
    Last Post: 10-23-2015, 05:06 AM
  2. Splitting a DB for different users
    By katmomo5 in forum Security
    Replies: 7
    Last Post: 12-19-2013, 02:50 PM
  3. Replies: 9
    Last Post: 05-11-2012, 11:18 AM
  4. Splitting Database
    By injanib in forum Database Design
    Replies: 0
    Last Post: 02-25-2011, 11:08 AM
  5. Database Splitting
    By Matthieu in forum Access
    Replies: 8
    Last Post: 02-08-2010, 03:37 PM

Tags for this Thread

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