# Always Test Destructive Changes on a Backup Copy

**URL:** <https://the.fmsoup.org/t/always-test-destructive-changes-on-a-backup-copy/3414>\
**Category:** Heads-Up!\
**Tags:** backup\
**Created:** [March 1, 2023, 1:12am UTC](https://the.fmsoup.org/t/always-test-destructive-changes-on-a-backup-copy/3414 "2023-03-01T01:12:45Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Malcolm](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/malcolm/32/196_2.png) [@Malcolm](https://the.fmsoup.org/u/Malcolm)\
**Post date:** [March 1, 2023, 1:12am UTC](https://the.fmsoup.org/t/always-test-destructive-changes-on-a-backup-copy/3414/1 "2023-03-01T01:12:45Z")

</div>

The Soliant team have just posted a new article, "[How to Split a Large File](https://www.soliantconsulting.com/blog/splitting-large-file-claris-filemaker/)".

# Do NOT do this experiment with any working databases!

The article instructs you to "Truncate Table" or to delete a table using the Manage Database dialog.

**NEVER DO THIS UNLESS YOU ARE WORKING ON A BACKUP COPY**

**Always backup before you may destructive changes**

Whenever you do any editing on multiple records, copy the affected records to a safe place before you make changes. When you make an error -- you will make an error one day -- you can easily correct the error using your backup.

I have sent a notice to the author asking them to include advice to create a backup and work on a backup. It should not be taken for granted.

@WimDecorte

---

<div class="post-metadata">

**Author:** ![Torsten](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/torsten/32/1574_2.png) [@Torsten](https://the.fmsoup.org/u/Torsten)\
**Post date:** [March 1, 2023, 3:57am UTC](https://the.fmsoup.org/t/always-test-destructive-changes-on-a-backup-copy/3414/2 "2023-03-01T03:57:51Z")

</div>

Huh - this reminds me of those videos where they do dangerous things and at the end say ‘don’t do this at home!’.

I’d say a developer would never do this on a live file without due backup. 🙂

---

<div class="post-metadata">

**Author:** ![Malcolm](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/malcolm/32/196_2.png) [@Malcolm](https://the.fmsoup.org/u/Malcolm)\
**Post date:** [March 1, 2023, 4:30am UTC](https://the.fmsoup.org/t/always-test-destructive-changes-on-a-backup-copy/3414/3 "2023-03-01T04:30:19Z")

</div>

> [@Torsten](#):
>
> I’d say a developer would never do this on a live file without due backup. 🙂

A developer knows. But someone inexperienced may not know better. They may think that there is an undo command.

P.s. I’ve already sent a message to the author asking them to add an explicit warning to work on a copy.