>>the Allways{BEFORE|AFTER} not sure, it is like the FINALLY in a TRY
>>catch, till today I do not understand why it's needed.
>
>It allows code to be executed if any of the CASE conditions are met. If they are, then some special preliminary code conditions can be executed, along with some follow-on cleanup conditions. But if none of those paths are executed, it's just ignored.

Ah! Now I understand, but the name is kind of misleading, I thought the code will execute regardless of any condition, and that is like placing the code outside the case and that is why I did not see the benefit.

>
>I have another one I've added for iterative blocks:
>

SCAN
>    * Normal SCAN...ENDSCAN code goes here
>
>    UNLESS condition
>        * You can test a condition here, and if it fails this code will be executed
>        * To restart the loop, issue RETRY
>        * In this condition you might make sure a table is open, or a resource is available
>
>    UNLESS condition2
>        * Several can exist
>        * In this one you might check another table
>
>    UNLESS conditionN
>        * Once all tests have passed, the loop begins like normal
>        * In this one you might check to see if the user's clicked the "cancel" button. :-)
>
>ENDSCAN
>

>
>There are several other ones: http://www.visual-freepro.org/wiki/index.php/VXB%2B%2B
>
>More keep coming.