لطفا منتظر باشید ...
Testing Finished Scripts
It's wise to test a script you've written to see if it performs as intended. However, even test runs can be dangerous if you don't take precautions. Procedures like modifying data in fields or deleting records can't be undone. Follow good testing procedures and you'll never experience the sinking feeling that comes with a misplaced or missing step.After the script runs, check the results carefully. Make sure that the proper records were found and that they were sorted correctly, that you end up at the correct layout, and that anything else you intended was handled properly.
To test a new script
1 .Choose File > Save a Copy As to make a copy of the database before running the script.This first step is the most critical one. If a script involves any actions that can't be undone, you should never, ever test it on your only copy of a current database. If the test goes as planned, you can delete the copy of the file after you check it.2 .In the "Create a copy named:" dialog box, choose "copy of current file" in the Save a (Windows)/Type (Macintosh) drop-down menu (Figure 10.1). Click Save.
Figure 10.1. The "Create a copy named:" dialog box lets you save a copy of your file before testing scripts that can alter data.
[View full size image]
Figure 10.2. Perform runs the selected script.
