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!

You live and Learn

Just found out something I didn't know re scripting.

If you are in the object about which you are scripting, you can omit the object name.

So, for example, if this is the ValueChanged event for FieldA, you DON'T need:

FieldA.Fill.Color.Red := 255 . etc

But can get away with:

Fill.Color.Red := 255 .

Show () .

Which saves some typing!

(I will also save some typing by NOT going back to old articles and blogs to adjust code. Sorry!)

More importantly, it means that a lot of scripts can be generic, as long as they reference the properties and methods of the current object, and that you are pasting them into objects that have those properties and methods.