Results 1 to 5 of 5
  1. #1
    alexandervj is offline Competent Performer
    Windows 7 64bit Access 2010 64bit
    Join Date
    Oct 2013
    Posts
    145

    Should I allow deletion of records, or just move them to somewhere else/hidden?

    Whats your opinion on this? I can see why both might be good. If you think I should just move the records aside instead of delete, do you know of a way to compress the data for those records so they don't take up as much storage space?

  2. #2
    naeemahmad is offline Advanced Beginner
    Windows 7 64bit Access 2010 64bit
    Join Date
    Nov 2013
    Location
    Riverside, USA
    Posts
    46
    We have a substantial amount of data being synchronized from field data on the front end interface. The data is often 'deleted' from the users point of view, but internally I am actually storing the 'deleted' data into a "Inactive" table for research in case of user mistakes or user wanting of the data back.

    To make this piece of "Inactivated" data have any significance, I have also added user fields and date fields which the user does not see to determine when and who 'deleted' the record in case of any training issues or reversal of the process.

    I have found that actually deleting data can leave you feeling as if you have also lost some potential research as to why the record was deleted.

    Of course you can always purge out data once you have determined there is actually no need for it.

    Hope this helped.

    Naeem~

  3. #3
    alexandervj is offline Competent Performer
    Windows 7 64bit Access 2010 64bit
    Join Date
    Oct 2013
    Posts
    145
    Yes, that helps very much, thank you!

  4. #4
    June7's Avatar
    June7 is online now VIP
    Windows 7 64bit Access 2010 32bit
    Join Date
    May 2011
    Location
    The Great Land
    Posts
    53,632
    If your db size is reaching the 2GB limit for Access, deletion of data might be an option but should be done only if absolutely no other approach is feasible and you really will never, never want to see it again.

    An option is to split db into front and back ends. If that has already been done, then can split the backend into multiple files the frontend links to. Or upgrade to MySQL or SQLServer.

    Regardless, the Access files should be Compacted and Repaired periodically.
    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.

  5. #5
    alexandervj is offline Competent Performer
    Windows 7 64bit Access 2010 64bit
    Join Date
    Oct 2013
    Posts
    145
    That makes sense, thanks June!

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

Similar Threads

  1. deletion with join
    By hklein in forum Queries
    Replies: 5
    Last Post: 05-01-2012, 03:41 PM
  2. Replies: 5
    Last Post: 03-02-2012, 02:47 PM
  3. Replies: 2
    Last Post: 02-29-2012, 12:51 AM
  4. Replies: 0
    Last Post: 01-18-2011, 07:09 AM
  5. Move records between tables
    By rogueakula in forum Access
    Replies: 1
    Last Post: 04-09-2010, 12:35 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