Results 1 to 8 of 8
  1. #1
    sparker75 is offline Competent Performer
    Windows XP Access 2010 32bit
    Join Date
    Jul 2018
    Posts
    107

    Force Close on update


    Anyone have any tricks to force close the database for users from the database when doing a data update macro?

  2. #2
    ranman256's Avatar
    ranman256 is offline VIP
    Windows Vista Access 2010 32bit
    Join Date
    Apr 2014
    Location
    Kentucky
    Posts
    9,525
    docmd.quit

  3. #3
    sparker75 is offline Competent Performer
    Windows XP Access 2010 32bit
    Join Date
    Jul 2018
    Posts
    107
    for users that are associated to a group?

  4. #4
    davegri's Avatar
    davegri is online now Excess Access
    Windows 10 Access 2016
    Join Date
    May 2012
    Location
    Denver
    Posts
    3,410
    We shouldn't have to play 20 questions here. What are you trying to accomplish? We can't guess.

  5. #5
    sparker75 is offline Competent Performer
    Windows XP Access 2010 32bit
    Join Date
    Jul 2018
    Posts
    107
    I would like to also add a kill function so when I run my update macro the users that are logged in the database will be forced closed. Allowing me exclusive access to the database.

  6. #6
    davegri's Avatar
    davegri is online now Excess Access
    Windows 10 Access 2016
    Join Date
    May 2012
    Location
    Denver
    Posts
    3,410

  7. #7
    Micron is online now Virtually Inert Person
    Windows 10 Access 2016
    Join Date
    Jun 2014
    Location
    Ontario, Canada
    Posts
    12,799
    You ought to give serious consideration to this idea if the db is for anything real important, such as maintaining compliance to an ISO standard, financial data or data upon which production decisions might be made. Kicking somebody out of their own front end in the middle of data entry may cause data integrity issues. While the db may balk when a call is made to close it and a record is missing data in required fields, it will still close when the Quit method is invoked. At least, that's been my experience. This could leave you with orphaned records and perhaps introduce corruption, in which case it doesn't really matter how important the data is if you corrupt the db. All the methods I've ever read about involve giving a user time to complete a task, which doesn't seem to be what you're after.

    Consider trying to open your updating db exclusively, and if you can, then run the update. No one will be able to get in while you have it open.
    The more we hear silence, the more we begin to think about our value in this universe.
    Paraphrase of Professor Brian Cox.

  8. #8
    GinaWhipp's Avatar
    GinaWhipp is offline Competent Performer
    Windows 7 64bit Access 2013 32bit
    Join Date
    Jul 2011
    Location
    Ohio, USA
    Posts
    377
    Hmm, I'm curious, is the database split? Because then you could notify the Users to shut down when they are finished and upon opening it should run your code to update the Frontend. I would not EVER throw them out, this will have serious consequences as previously mentioned. And the does not count the angry Users!

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

Similar Threads

  1. Replies: 5
    Last Post: 01-17-2017, 02:12 PM
  2. Replies: 7
    Last Post: 07-19-2016, 05:28 PM
  3. How to force an update
    By bginhb in forum Forms
    Replies: 14
    Last Post: 12-04-2015, 07:00 AM
  4. Force update of unbound calculated control
    By LillMcGill in forum Forms
    Replies: 7
    Last Post: 04-15-2013, 06:51 PM
  5. A way to force Access to update external file?
    By gkun in forum Import/Export Data
    Replies: 0
    Last Post: 10-27-2009, 06:11 PM

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