CATEGORY: Troubleshooting
CLASS: Basics
VERSION: All Current Versions
By almost all measuring sticks, data loss is the greatest fear in a database crash, programming bug or error by a data entry person. There isn’t any way to totally guarantee against data loss but a developer can take measures to protect data or restore it.
The number one focus of the developer needs to be the backup. A process of creating copies of files and storing them in a remote location in case of emergency. FileMaker files should be closed before they are a part of any backup. FileMaker Server can make backup copies of files while they are being hosted and can do it on a defined schedule.
The other number one focus (love it when I say things like that) is security within the solution. Users that shouldn’t have the ability to delete records should be protected from doing that by mistake.
As a developer, you should continually monitor actual and potential data loss situation and you should monitor ways to increase the frequency of your information backups.
Here are some links to other posts that might be of interest in regards to this topic...
Save! Save! Save! Backup! Backup! Backup!!
Delete Confirmation
EXAMPLE: Out Of Control Cascading Deletes
Create, Delete And Revert Records
Delete Record / Request Script Step
The Delete All Records Script Step
Cascading Delete Breakdown
====================== ADVERTISEMENT ==============================
To check out the online FileMaker Crosswords, please visit http://www.dwaynewright.com/crossword.html===================================================================
Posts
