Tuesday, 16 February 2010

Getting Round The Crash

I'm sure you know this one, don't you?

If, in any Windows version of DataEase or Ffenics, you are happily developing away and you get the dreaded "Exception" message to tell you that all the work you just didn't save is heading down to Rio, then:
  1. Curse
  2. Curse again
  3. Click the DataEase or Ffenics screen behind the message BEFORE you click ok, and
  4. Go File -- Save/Save As, etc
  5. Now click the GPF ok button to bomb out of your application.
You might even find you can continue working for a bit with that dialog box on screen ... but you might not get a second chance, so save, bomb out, and jump back in again.

Can 't guarantee it will always work, but as you only lifeline when this happens, always worth trying!

1 comment:

  1. I like it ... but surely one of our big problems as developers is the maintainability of our code once we're not around personally.

    While saving on typing has its benefits, surely the additional typing, and it is a small saving in this case, makes what the developer intended absolutely clear to those who must follow in his/her footsteps. Such was the rationale for adding comments to Fortran code and its value has not decreased (even though I must be one of the few people who can still code in Fortan II), and commenting is a habit that IMHO is well worth developing for the sake of clarity.