Although I've tried my best to discourage it, my client is convinced that he wants to delete employees that were terminated years ago. This company started with Solomon when it was still independent and PC-based so they are dragging around a LOT of history. Is there an "approved" way to do this?
*This post is locked for comments
The approach suggested by Walt is what I do with my clients as well. I make a SQL backup of the database and restore it into another physical database file and then add it as an archive company. I then run some update queries to change the CpnyID in the various employee tables for this archive company. Finally, I go into access rights maintenance and change the rights to read-only so that nothing can be modified through the SL screens. That provides the protection needed to avoid accidents yet leaves the data available should it be needed for an audit.
I am assuming you know all the payroll tables that will need the update query run against them.
My first thing would be to create a historical back of the database(s) seperate from the routine bu's that should be happening. That way, if needed, you could get back to the historical data. That in mind, I might consider putting a copy of this bu into a secondary company that could be accessed, but, I would stripe all users except for a required few from access, so that mistaked don't happen... easily.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,253 Super User 2024 Season 2
Martin Dráb 230,188 Most Valuable Professional
nmaenpaa 101,156