George,

I guess it depends on the definition of abuse. This one isn't too bad:

   .nAnchor = iif( .chkVertical.Value, 512, ;
                 icase( .opgTop.Value = 1, 0, ;
                        .opgTop.Value = 2, 1, ;
                        .opgTop.Value = 3, 16 ) + ;
                 icase( .opgBottom.Value = 1, 0, ;
                        .opgBottom.Value = 2, 4, ;
                        .opgBottom.Value = 3, 64 ) ) + ;
              iif( .chkHorizontal.Value, 256, ;
                 icase( .opgLeft.Value = 1, 0, ;
                        .opgLeft.Value = 2, 2, ;
                        .opgLeft.Value = 3, 32 ) + ;
                 icase( .opgRight.Value = 1, 0, ;
                        .opgRight.Value = 2, 8, ;
                        .opgRight.Value = 3, 128 ) )

But this one is another case, (and actually isn't quite correct)

   lcRetVal = icase( pnThis = 1, icase( pnOther = 1, "fixed", ;
                                        pnOther = 2, iif( plNative, "moves", "fixed" ), ;
                                       "moves %" ), ;
                     pnThis = 2, iif( plNative, "fixed", "moves" ), ;
                     "moves %" )

Before I left on vacation I was working on a corrected version and it's gotten a bit gnarlier.

At least there is some indentation to help see what is what in all that mess. *s*

>< s >OK, I will. Knowing you a bit, I doubt there's much abuse.:-)