RESCUE FOR 4D DOCUMENTATION - Advice

• Listen to the advice of Doctor unless your problems persist. In fact the advice of Doctor always favours security. But in some cases, too much security prevents indispensable repairs.
  
  
  
• Visit our FTP site and Lists frequently because we may move Rescue for 4D permanently (as per the movements of 4D and as per of your wishes).
  
  
  
• Keep us informed about your wishes, questions, and problems because this product is made for YOU.
• It's advisable to enable all the options enabled (except, perhaps, the warning) such that the Doctor and the Editor have the maximum power.
  
  
  
• Don't utilize the product below the recommended memory size. Rescue for 4D has been tested with structures of 30 MB (4D Resource) and the recommended memory size is suitable for almost all structures.
  
  
  
• The greater the buffer disk size, the faster you can work.
  
  
  
• Virtual memory, RamDoubler and Optimem don't seem be a problem for Rescue for 4D. Yet, in case of strange reactions, don't hesitate in disabling them.
  
  
  
• It's better to expend the compacted databases with Autodoubler before using Rescue for 4D.
  
  
  
• If you are using Aaron, you may experience strange reactions with the scroll bars. Deactivate Aaron (Sorry).
  
  
• In Editor, don't delete anything you don't know. The results could be serious even if Rescue for 4D refuses the deletion of some essential types. (Warning).
  
  
  
• Always restart Doctor after you make deletions.
  
  
  
• To avoid bad information, Rescue for 4D ignores the trash table of 4D. That authorizes it to correct problems as the resources overlap. Yet, when you have used Rescue for 4D and have deleted resources, make a compacting with 4D Utils and this last one will update the trash table. (Warning)
  
  
  
• Some error types, such as the Headers errors must ONLY be corrected WITH Rescue for 4D. Of course, this error type is, in general, a sign that the resource isn't where 4D was expecting it. A correction with 4D (deleting a procedure for example) can damage one or more resources. Rescue for 4D corrects this kind of problem without introducing new problems because it doesn't affect the table of free spaces. (Trash Table). (Warning)
  
  
  
• You will not be able to use this version of Rescue for 4D to delete files and fields. However, a future version, Rescue for 4D Pro, will allow you to make such changes (and many other things, too).
  
  
  
• Always start the Doctor with a Log. This log will inform you about the state of your structure. You may then decide whether or not to effect repairs.
  
  
  
• You must have the reflex Crash 4D -> Rescue for 4D. In fact, if you crash while programming, it's quite possible that your structure may be damaged. Check it before it is too late.
  
  
  
• Regular checking can prove useful. Problems which occur may not be evident at the time of the crash.
  
  
• Don't wait for a miracle from Doctor. Doctor functions by analyzing each case ; and each case is different. This is why your problems interest us. The strength of this product will, in large part, come from your comments and suggestions.
  
  
• This software is made for you. It was originally intended for internal use by JCS Développement.

 

 

---

The services rendered by Rescue for 4D have proven to us that it will also be beneficial to you.

 

So, DON'T PIRATE IT !

 

Development of a product such as Rescue for 4D necessitates several months of implementation. Its movement depends not only on your requests, but also on your financing.