Browse By Tags

  • sage 50 database verification tool has found a problem in your company file that it was unable to fix

    Sage 50 is not allowing me to go in new year and shows the message to check the data integrity through Advance database check. While following the message, it shows the message "sage 50 database verification tool has found a problem in your company file…
  • Option to export all Data since the last valid Backup when unfixable Database Errors occur

    When Errors occur in the Sage Database, if these cannot be repaired then the only viable option is to restore to the last valid Backup. However, the users have to first Print out any Data that they have entered into Sage since the last valid Backup and…
  • Looking after your data - best practice

    To protect your Sage Accounts data we recommend checking your data and backing up regularly. We've dedicated an area of the Help Centre to this very subject, covering data checking, scheduling backups and much more. Check it out now >
  • Looking after your data

    To protect your accounts data we recommend you run the Check Data option and back up your data on a regular basis. Find out more in the Help Centre where there's a topic dedicated to data protection. Read more >
  • Protect your data the easy way

    Taking data backups doesn't have to be a chore. You can use the Backup Manager to make regular backups automatically. Meaning no more staying behind to back up, or waiting for others to log out. Read more
  • Protecting your Sage 50cloud Accounts data

    To minimise the risk of data corruption and the impact it has on your business we've pulled together some recommended best practice. Read more >
  • Cryptoware Backup Issues

    FormerMember
    FormerMember
    We received the Zepto cryptoware from a lovely e-mail and it hit us hard. After wiping and restoring a backup we are still having trouble printing checks and the invoice formats were all erased. Luckily all of our data is in there still. The IT guy is…
  • Disaster Recovery

    Is there any documentation outlining what needs to be backed up for Disaster Recovery? SQL backups are done, but what happens if the server is lost? What steps can one follow to recover a system having only the SQL backups?