>>Figures! ;) But I that code is a bit flawed because if you actually click
>>OK on the print dialog, the laError array doesn't get created (no error!).
>>Another "duh". Perhaps I'll go a special print class after all. Sigh.
>
>

>ON ERROR llError = .T.
>llError = .F.
>*Call print dialog
>IF llError
>   AERROR(laError)
>   *etc.
>ENDif
>

Garrett,

It seems risky to be using ON ERROR in method code, or in any UDF that operates in a OO context, because any Error method in the program stack will take precedence over ON ERROR. Unless it is stipulated that no objects in Steve's application have any Error method code, I would advise against the ON ERROR approach and go back to your earlier suggestion of using a custom command button with an Error event.

Mike