play makAll work and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. All HBAM2016AUG95HPro 3.0 All work and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. All work and no play makes Jack a dullCopyright 1984-1996 Claris Corporation and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. ::A+@@C9E8G7I6K5M4A3C2E1G0I/K.M-,@*BD F H J L NPRTVXZ\^`bdfhjlnpr t!v"x#z$|%~&@'B(D)%~&@'B(D):HBAM3016AUG95@AAzHH(FG(HH(d'hzA'dAWhy does the recover command sometimes need to be used? A little background regarding how FileMaker Pro maintains files during usage sheds some light on how databases can become damaged. FileMaker Pro is a disk-based application, in that FileMaker Pro does not need to load the entire database into RAM as the file is opened. The application contains code that manages the transfer of data from the hard drive to RAM and back. The memory allocated to FileMaker Pro under MultiFinder or System 7Q4 1st Quarter 2nd Quarter 3rd Quarter 4th Quarter,  , X5 9AWhy does the recover command sometimes need to be used? A little background regarding how FileMaker Pro maintains files during usage sheds some light on how databases can become damaged. FileMaker Pro is a disk-based application, in that FileMaker Pro does not need to load the entire database into RAM as the file is opened. The application contains code that manages the transfer of data from the hard drive to RAM and back. The memory allocated to FileMaker Pro under MultiFinder or System 7B is divided into two portions: application code, and data from the file itself. As the file is used, FileMaker Pro will routinely write updated sections of the file from data buffers in RAM to the hard drive. By far, the most common cause of file damage is an unexpected application termination. In most cases, an unexpected quit will occur at a time when the file has been idle since the last hard drive update. In this situation, the next time the database is opened, FileMaker Pro will run a:+|W+XwiUU GG3/22/97@TEXT TEXTLOCKEDD ATextB GXXLook in Define Fields to see how to prevent modifications once a value has been entered.A2(=10)A?2A TextLockedB AAG@@@ A Layout #1@@A Layout #2A Layout #1B$$$$@,iI $,.Yesf@No?@/,  , : AM PMl  w 2E )@2A Layout #2BV!A2 ;2 @BA+l\How a file can become damaged and what you can do to avoid having to recover a damaged file. @BA+Ab as if you were going to the next field in a layout. Then try and modify your entry. @BA)+ !* Bo show }bind put } if % % Used to snap to device pixels, 1/4th of the pixel in. /stp { % x y pl x y % Snap To Pixel, pixel (auto stroke adjust) transform 0.25 sub round 0.25 add exch 0.25 sub round 0.25 add exch itransform } bind def /snapmoveto { % x y m - % moveto, auto stroke adjust stp moveto } bind def /snaplineto { % x y l - % lineto, auto stroke adjust stp lineto } bind def  .#1,#C8#fff )# )# (#ٙٙٙ (#fff # #ٙٙٙ #ٙٙٙ 1)#fff (( D#fff (#̌̌ (#wwwwww )#ffffff )#ffffff ++#wwwwww ))#̌̌ ))#UUUUUU0 ##ffffff0$#wwwwEww0$#@@@0 "#̌̌ !# "#fff "# "#ٙٙٙ ##ٙٙٙ ###fff ""# "" F#̌̌ !! R Q"1wq  wp#HH^ff33̙ ff 33 ff33ffffffffffff33ff33333333ff333333 !ff"33#$%G&'ff(33)*+,̙-ff.33/0̙1̙2̙3̙ff4̙335̙6ff7ff8ff9ffff:ff33;ff<33=33>33?33ff@3333A33BCDEffF33GHIJKffL33MNOP̙QffR33STUVWffX33YZff[ff\ff]ffff^ff33_ff`33a33b33 Hc33ffd3333e33fghiffj33klffmffnffoffffpff33qffrffsfftff̙uffffvff33wffxffyffzff{ffff|ff33}ff~ffffffffffffffffffffff33ffffff33ff33ff33ff33ffff3333ff33ffffffffffff33ff33333333ff333333333333̙33ff33333333333333ff33I333333ff33ff33ff33ffff33ff3333ff3333333333333333ff333333333333333333ff333333ff33̙ff33ff33ffffffffffff33ff33333333ff333333ff33ٻڪۈwwUUDD J""wwUUDD""wwUUDD""wwwwwwUUUUUUDDDDDD""""""wp$       $      K )      0       9'        =/        A*           G+           H          J          L N@            P      2        Q                P      .        Y   :             T             M   S  0                   T 8                 X;                    V:;;::                 \ :;:;:;   *              _-:;::;:;       N       ^  V ;::;:;:  "              Z7::;^;:;:;:                T;;:;;:;:::;              \=:::::;:;;::;;           443  W85:;:;::;;:;:;::@:            O X6d_;4;;::;:;d:;:@;@:          5  W5^_::5;;;:;@;A:;@:@:        4     V; _^:;:;:4:;::;@:@@:    ^X4   P :"_;:5:;:;;:__:A:@@  4     S.;e^:;5;::::;:;A^@@   4զ    N;܎݈^;::4;:;:;_@ 4  P     4  W ܈Љ^;;4:;:;  ^ 4    ^ R܈T^^;:;:;5;:;@ 4        V,4dTT]^Ў~~TT^^:;;;:;  Xզ      X:ddVxTVTd :]d~TTe:;:;: 4զ     5]4   _ 9dddjzyzTx]d  ^TЈd;:;4   4X   X    e /݈ddddc]zUQ܈d^9 ]d:  ^    ֦   d;  29ddcddd]9 ^jddjd:; 4     5    i: 99dd܈W]^ddddddjddd:: 4    X    _: 4^d99dWK]^d dddjd ddd;:; ^ 4     l; dd@99dd]WKWK݈ 3]jddddd; 3   4֦ 4     c; R^dd@9ddd^KK] 3]dd d;:   4     i;_ 3^djddd]ddd3]d:;:: 4  4զ    X  m4; 4^dddddd^3 : d:;   4 43      c :44;^:4ddjjddjdd^3^ ddd;         f&5;;;:dddddddjdd;; ^   S   e!:5445::5::djddd dd;  X    X  f- ;::;::9djdddjdddd;  XX  X   i):5;43;::4;:;::ddjdddddd:  4    ֦ 5   k+:;4::;:;::;:;;4ddjjdd:; 4X   4        f" 4;;5;:^;:::dddddddd T: 4  4X     b;/:;^4;^;;;;;:dddddd;4; ^  4  i,:;;^Ц:;:;;;^ddddddd:; 4  4ի    4  i :::;:::;:ddddddd;    4զ  ^  i $^:;;;;;:;^ddddddd:;^  4W       f  5;:;;:U:;::dddd dd ^        j :^::";:;4:;:dddddddd;;  4֦ 4   4  d   2;^:::_;4;::dddddddd 4ɦ   4   i? 4:4Љ:;;::;;:ddddddddd;;  4ɦ    4  i 9 ;::;;;;4dddddddd::_ 4       p@ V  :^Ϫe;5;:4ddddddd^;:;: 4      5      n 9:;:^::4dddddd^;: X^  5  4W     oC 44  ;;:;^_:;;4dddd ;; 4  ^       pE ^;:::;;;4dddd4e: ^  4 5    sF:  :;:e::;;4Wdd^ :   4   4^ mD 4 54_4 ::;;;:4d^: .  4      sG ;:4d4_e:e:;;  4  ^3   ɥ   u  :4 X6: 5:;:4^ 4d;;^:;   4     4   n? ;:5  ^:;;;4^;:e;   X4   X  |  44;4%; 4 4^; :_4  4    ^    q%  ;54;:4#;:;  4d; :;d: 4   4  xN+2  ;;4_;:5  ^: :;;:  4        %++, 4  1 ;4444^::; ^ 4_ ::;;; 4W  Y     ~,+ ,   ;*:^^;4;: ^ _d ::;;  4     4X    ~+,+,+9,3   ;4d^::; ^^:::::_:: X4  ^  4    ++<,+,+2 X^4;:; _ ^4de:4 4    5 4 z +,+++ ,-:4#45 ;^:^;  Z^  X   ^  %C,+,+,++,,3   ;:;;:  :54   4      ,++,+3&;4:;  4_:: 4   ^      } +++, 34 #:_:  ;de^;4;;:         W   ++,++,,3:_: [:_: _Љd;:;4^:;  4    4  ,,++,+-3;de_4 ; 4:;:;;4;  4   4 4 !%%+++,++,+,3;:_^:  : ;^d_d;:4_:  4   ֦ ;4 %%++++,,,3;:;dѬ^ ^^d::;; Xզ        \++,,++,3;;:e^d^_ :e^;:;;  4     5Ϧ  %++,++,+, 3:;;:ded^ Љ^;:;^;:  4     X     %+,+43;;:;_^:^d;:;:^Љ ^   4 X 5   ,+++ ,+,,,-3;;::^;^ede:_:^:] 4  ֲ 44    %,++++83:4;;:;:;:;:_::d ;_4 W:  4զ      %++ ,+,++,+,+,,3:;^;;:;:;:;4;4:^ :  4       #%%%,,+,+,+,35:;::;4_ XW    44      ^+++,+,,,3:5; :         4    +%+,++,34554e4:;^;   4 4  4  ^   %+,,+,+,++-;4^:54;:4;      ^   %+,,++,+,+3:5::_ ;4 ;45  Xզ   4  :   w,++! ;5445;5 4       ,+,+,+,++,+,++, 3  :4X;^    X3   4  %+,+,++,23:;4^ 545 4   4     `++,+,++,,3; :;^^4  4   4  4; 4   +,++,+,,23;:;:5 4___4 ^_        %%,+,+,++3 ;:::4 :: ;^; 4      _    ++,++,+,,, -  5^;a ^; 4e4_: 4        ~ ,,+,+2  4:;:4 535;֧ 4       z,+++,+,+ ,,P-  ;::;:;4: X3  4 ɂ 4  }+,+,+ ,,23  $ 5::; 4:;;     :5  3   s%++,,+,3 5:^ b::;::;:4;;45: 4  _ ɦ 5  |%+,++,+,2 (^  ::;;:4 ;^5;     4֦  ɦ 54  u+++,,2P 3 5:   : ;    4     p,+,P,  4e : ;:;:: 4   4ɦ  ɲ    u,,+,++,,2223   ; 4;:;:c   45 4Ղ    n++,, 4   ; 4:;::;4  : 4ς  4   q%+,+,,3    ;4: :;;;  4 4զ  4    h+,+,22V 5  :e:  :;:;:  ^ 4ς 44    f+ ,+,,2V   ;d_:;:;;  5^ 4   l d+,2- %4 45::_d::;:;;  4 4զ   e+,+, (  ;^;e^ ::;  X^ 4   i++,,2- 4  5^d;4e ;;: : 4^      d+,,2V   :^::e^:;:  4: 44 Xɂ 4  a++,,P3  3  ;d_e^ 45 4 4 X e4   c %+,2V 4 4  ;__e 4:ed5 4^ X 5   b,+,23 '44  4:de_^ :_ ^4 W    ],2P 5  :;d;^Љ;^_: WX X]    T,+,,-   :;^d  : X: ]   X+   :^^_ 5Ϧ WX   Z f,3   5;^:;Ђ :   X+,3 %   ::^4ς ^    P,   5;4^; ;ς W^ 5  H++3  :;: :ς ^   I+- ;;;:;  4ς 4   J4, $  ;d 5Ђ W  D ,-g ;^ :Ϧ    G+ +3   A  5    C$+,3   :4 :4    XBV    ; 4 4 4  +;2   ; ;: =+    4  ;: >4       +=   :       h=   ;     +:  ^       ++8+ 5F    ,7 ;     3+   +-    "4   #+ :  !++V  2; *+Vi  +X(,V U,&++OV+eUVd$ 2X  V+ V  j#  .1 9  # */#`T_HH``ff33̙ ff 33 ff33ffffffffffff33ff33333333ff333333 !ff"33#$%&'kff(33)*+,̙-ff.33/0̙1̙2̙3̙ff4̙335̙6ff7ff8ff9ffff:ff33;ff<33=33>33?33ff@3333A33BCDEffF33GHIJKffL33MNOP̙QffR33STUVWffX33YZff[ff\ff]ffff^ff33_ff`33a33b33c33ffd3333 le33fghiffj33klffmffnffoffffpff33qffrffsfftff̙uffffvff33wffxffyffzff{ffff|ff33}ff~ffffffffffffffffffffff33ffffff33ff33ff33ff33ffff3333ff33ffffffffffff33ff33333333ff333333333333̙33ff33333333333333ff33333333ffm33ff33ff33ffff33ff3333ff3333333333333333ff333333333333333333ff333333ff33̙ff33ff33ffffffffffff33ff33333333ff333333ff33ٻڪۈwwUUDD"" nwwUUDD""wwUUDD""wwwwwwUUUUUUDDDDDD""""""T^*/$+ + +*VV,++++)+VV)o*V))%&++%VV#&+VV$V0VV+1+ pV0VV+0V+V/VVV.+$V$+"VVVV+ +V+q V&+%+,+VUU.+VU1+UU0UU7 V+VV%VU UUUU! rUUUUUUUUUU*UUUUUU*UUUU**U U UUU UUUUU# A ##  H#KHH4bff33̙ sff 33 ff33ffffffffffff33ff33333333ff333333 !ff"33#$%&'ff(33)*+,̙-ff.33/0̙1̙2̙3̙ff4̙335̙6ff7ff8ff9ffff:ff33;ff<33=33>33?33ff@3333A33BCDEffF33G " tHIJKffL33MNOP̙QffR33STUVWffX33YZff[ff\ff]ffff^ff33_ff`33a33b33c33ffd3333e33fghiffj33klffmffnffoffffpff33qffrffsfftff̙uffffvff33wffxffyffzff{ffff|ff33}ff~ffffffffffffffffffffff33ffffff33uff33ff33ff33ffff3333ff33ffffffffffff33ff33333333ff333333333333̙33ff33333333333333ff33333333ff33ff33ff33ffff33ff3333ff3333333333333333ff333333333333333333ff333333ff33̙ff33!# vff33ffffffffffff33ff33333333ff333333ff33ٻڪۈwwUUDD""wwUUDD""wwUUDD""wwwwwwUUUUUUDDDDDD""""""Kw$H$V+"V++/--+V-+V,VV-,-"$ x.-+.+*/.V0VCVQV+Zy V++ +VZVV+NVX+VV+V+++#% zVV+VR+VCHFV+VHVV VE{+VAVAV>V@DVVBGV$& |+++G+VIV+VL+VfV+VVV; +V}#  .# "? # ? ?#@@@ U U#@@@"?   g"IO, Palatino .* Steve Davis#  #%' ~JO) Steve Davis# @ ."] "Y # Y Y#@@@ m m#@@@"Y   "cm)Databases By Design#   #dff)Databases By Design#   U#y9 (5720 Kayron Drive# #y9)5720 Kayron Drive# u ."J "s R#"s # "s_ #"~ R   S"z&( @)Atlanta, Ga. 30328#  #y)Atlanta, Ga. 30328# pu ."H "slR#"sl # "s #"~lR  z {"N)Phone / Fax: (404) 705-9440#  #AN)Phone / Fax: (404) 705-9440#  ."m " y#" # " #" y  k "X)e-mail: dataman@mindspring.com#  #X)e-mail: dataman@mindspring.com') B#  ." #" # " #   ""7! ( Solution By# #7!) Solution By# 3 ." "2 ,C#"2 # "39#"; ,  6s ")Member# #)Member#  ." "#"# "#( D"  6i F")Claris Solutions Alliance# #)Claris Solutions Alliance#  ."A "K#"# "#"K,O@ HelveticaGenevaPalatino@+A+PICTA. .y%PostScript Hack by Mike Brors 12/7/90 /DisableNextSetRGBColor { userdict begin /setrgbcolor { pop pop pop userdict begin /setrgbcolor systemdict /setrgbcolor get def end } def end } bind def /bcarray where { pop bcarray 2 { /da 4 ps div def df setfont gsave cs wi 1 index 0 ne{exch da add exch}if grestore setcharwidth cs 0 0 smc da 0 smc da da smc 0 da smc c gray { gl} {1 setgray}ifelse da 2. div dup movet wAd' )@ ,d-*@ AB  @openAopenE7>@D@AQBUUX  w $,.Yesf@No?@/,  , : AM PM.,Mndergoing structural changes should be treated somewhat conservatively. It's a good idea that any major changes to a file, including field deletions or modifications, be done in a clone of the database which can be refilled with data via an import after the design work is done. The importance of using a clone for design modifications increases as the database size grows. Timely back-ups are the only guarantee of database integrity and data safety. Using the FileMaker Pro recover command Nis like tossing a life-saver to a person who cant swim; it will probably save the person, but it would have been more prudent to keep them from getting wet in the first place.ving rotating back-ups can accomplish this. This method involves separate back-up copies over no less than a two week rotation. The file is backed-up to a set on day one, a new set on day two, until ten sets of back-ups exist assuming a five day work week. On the eleventh day, the first set is reused./-Kom a find or are sorting in unusual orders should be fixed by recovery. Keep in mind that there are many other conditions that will result in incorrect finding or sorting, including mismatched field types. Be certain you have eliminated all other possibilities before recovering a file. With FileMaker Pro 2.1v2 or older, recovering a file WILL reset any custom ordering in the database to the creation order; this reordering affects the layout pop-up list, the Scripts menu, and the field listL in Define Fields. Databases relying on custom orders will require manual reordering after a file recovery. With FileMaker Pro 2.1v3, including file recovery in the regular maintenance of a file may help to correct file structure problems before they become apparent, without the need to manually reorder custom lists following the recovery. This recommendation should be balanced against the argument whether less intrusive methods (compression and backing-up), are adequate. Files that are u0.I In cases of multiple corrupted files on a hard drive, the hard drive itself may be the culprit. Check the health of the hard drive with a drive utility program. Software that optimizes, compresses, or partitions the hard drive should be current version. Driver software must be compatible with the System version. In most cases, no maintenance beyond frequent back-ups is necessary. However, most databases are good candidates for a routine compression. Saving a compressed copy rewrites the Jentire database, fitting as much data into each block as is possible. This procedure not only reclaims unused space in the file, it also rebuilds the files structure. Compression can be time-consuming and might be best accomplished as an overnight task. In general, recovering a file should be reserved for files that will not open, or are displaying obvious index problems. Field indexes are used by FileMaker Pro for finding and sorting. Databases that are returning records incorrectly fr1/G file is running is the best way to avoid damaging a database. In general, commercial extensions should not be a problem as long as an almost religious commitment to running current versions of this software is maintained. Of course, any public domain or share ware extensions should be avoided. Even the use of commercial extensions should be conservative on the machine responsible for running the database. System stability and the number of active extensions are inversely proportional. If Hthe file is being used in an area subject to power outages, an uninterruptable power supply (UPS) is strongly advised. The cost of a UPS might equal the time involved in one file recovery. FileMaker Pro limits database size to 32 megabytes. Files that have exceeded that limit will be damaged beyond repair, since it is likely that key elements of the file structure will have been obliterated by overwriting. File sizes should be managed through archiving methods to avoid the size limitation.20E This type of rotation ensures that a lurking problem will not spoil your chances of an undamaged file restoration. If new data entry has been minimal since the last back-up, with large files it may be more efficient to simply use the back-up rather than going through a time-consuming recovery. Many programs are available that ease the drudgery of routine back-ups. Using a back-up program that allows file or folder specific back-ups will provide the most efficient protection of important dFatabase files. Periodically saving a clone will provide a master copy of the database structure which can be useful for restoring scripts or layouts that may be deleted in the recovered file. In many cases, it is a good idea to save a clone of the file and a back-up at an off-site location, should the disaster not be limited to the file itself. Since unexpected application termination is the most common cause of database corruption, avoiding unexpected quits on the computer from which the31C consistency check on the file. Typically, the file will open without problems. However, if the unexpected quit occurred during a hard drive update, the file is likely to be in an inconsistent state, and require repair measures the Recover command provides. File corruption is not inevitable, but its a good idea to take measures to prevent damage to a database and also ensure that databases are properly backed-up in case of disaster. Routine back-ups are imperative with any database. MagnDetic media has a sometimes transitory nature; entropy surrounds us and our data. A good back-up program should provide multiple copies of a database as sources for restoration. A scheme involving rotating back-ups can accomplish this. This method involves separate back-up copies over no less than a two week rotation. The file is backed-up to a set on day one, a new set on day two, until ten sets of back-ups exist assuming a five day work week. On the eleventh day, the first set is reused.42AWhy does the recover command sometimes need to be used? A little background regarding how FileMaker Pro maintains files during usage sheds some light on how databases can become damaged. FileMaker Pro is a disk-based application, in that FileMaker Pro does not need to load the entire database into RAM as the file is opened. The application contains code that manages the transfer of data from the hard drive to RAM and back. The memory allocated to FileMaker Pro under MultiFinder or System 7B is divided into two portions: application code, and data from the file itself. As the file is used, FileMaker Pro will routinely write updated sections of the file from data buffers in RAM to the hard drive. By far, the most common cause of file damage is an unexpected application termination. In most cases, an unexpected quit will occur at a time when the file has been idle since the last hard drive update. In this situation, the next time the database is opened, FileMaker Pro will run a53Mndergoing structural changes should be treated somewhat conservatively. It's a good idea that any major changes to a file, including field deletions or modifications, be done in a clone of the database which can be refilled with data via an import after the design work is done. The importance of using a clone for design modifications increases as the database size grows. Timely back-ups are the only guarantee of database integrity and data safety. Using the FileMaker Pro recover command Nis like tossing a life-saver to a person who cant swim; it will probably save the person, but it would have been more prudent to keep them from getting wet in the first place.involving rotating back-ups can accomplish this. This method involves separate back-up copies over no less than a two week rotation. The file is backed-up to a set on day one, a new set on day two, until ten sets of back-ups exist assuming a five day work week. On the eleventh day, the first set is reused.64Kom a find or are sorting in unusual orders should be fixed by recovery. Keep in mind that there are many other conditions that will result in incorrect finding or sorting, including mismatched field types. Be certain you have eliminated all other possibilities before recovering a file. With FileMaker Pro 2.1v2 or older, recovering a file WILL reset any custom ordering in the database to the creation order; this reordering affects the layout pop-up list, the Scripts menu, and the field listL in Define Fields. Databases relying on custom orders will require manual reordering after a file recovery. With FileMaker Pro 2.1v3, including file recovery in the regular maintenance of a file may help to correct file structure problems before they become apparent, without the need to manually reorder custom lists following the recovery. This recommendation should be balanced against the argument whether less intrusive methods (compression and backing-up), are adequate. Files that are u75I In cases of multiple corrupted files on a hard drive, the hard drive itself may be the culprit. Check the health of the hard drive with a drive utility program. Software that optimizes, compresses, or partitions the hard drive should be current version. Driver software must be compatible with the System version. In most cases, no maintenance beyond frequent back-ups is necessary. However, most databases are good candidates for a routine compression. Saving a compressed copy rewrites the Jentire database, fitting as much data into each block as is possible. This procedure not only reclaims unused space in the file, it also rebuilds the files structure. Compression can be time-consuming and might be best accomplished as an overnight task. In general, recovering a file should be reserved for files that will not open, or are displaying obvious index problems. Field indexes are used by FileMaker Pro for finding and sorting. Databases that are returning records incorrectly fr86G file is running is the best way to avoid damaging a database. In general, commercial extensions should not be a problem as long as an almost religious commitment to running current versions of this software is maintained. Of course, any public domain or share ware extensions should be avoided. Even the use of commercial extensions should be conservative on the machine responsible for running the database. System stability and the number of active extensions are inversely proportional. If Hthe file is being used in an area subject to power outages, an uninterruptable power supply (UPS) is strongly advised. The cost of a UPS might equal the time involved in one file recovery. FileMaker Pro limits database size to 32 megabytes. Files that have exceeded that limit will be damaged beyond repair, since it is likely that key elements of the file structure will have been obliterated by overwriting. File sizes should be managed through archiving methods to avoid the size limitation.97E This type of rotation ensures that a lurking problem will not spoil your chances of an undamaged file restoration. If new data entry has been minimal since the last back-up, with large files it may be more efficient to simply use the back-up rather than going through a time-consuming recovery. Many programs are available that ease the drudgery of routine back-ups. Using a back-up program that allows file or folder specific back-ups will provide the most efficient protection of important dFatabase files. Periodically saving a clone will provide a master copy of the database structure which can be useful for restoring scripts or layouts that may be deleted in the recovered file. In many cases, it is a good idea to save a clone of the file and a back-up at an off-site location, should the disaster not be limited to the file itself. Since unexpected application termination is the most common cause of database corruption, avoiding unexpected quits on the computer from which the8C consistency check on the file. Typically, the file will open without problems. However, if the unexpected quit occurred during a hard drive update, the file is likely to be in an inconsistent state, and require repair measures the Recover command provides. File corruption is not inevitable, but its a good idea to take measures to prevent damage to a database and also ensure that databases are properly backed-up in case of disaster. Routine back-ups are imperative with any database. MagnDetic media has a sometimes transitory nature; entropy surrounds us and our data. A good back-up program should provide multiple copies of a database as sources for restoration. A scheme involving rotating back-ups can accomplish this. This method involves separate back-up copies over no less than a two week rotation. The file is backed-up to a set on day one, a new set on day two, until ten sets of back-ups exist assuming a five day work week. On the eleventh day, the first set is reused.D>EPro 3.0F!Wt-2(M1,,./: AM PMYyTtNnFfNALL OTABSP^SundayMondayTuesday WednesdayThursdayFridaySaturdayJanuaryFebruaryMarchAprilMayJuneJulyAugust SeptemberOctoberNovemberDecemberQ1Q2Q3Q4 1st Quarter 2nd Quarter 3rd Quarter 4th Quarter,  , X5