>>>Hi everybody,
>>>
>>>It seems like if there are some errors in Report, they are not trappable and if I run this report through application, I can not determine, what causes them.
>>>
>>>My question is: can we trap them and if no, can this functionality be added to new version of VFP?
>>
>>Doe untrappable REPORT errors it is impossible to use REPORT command in a vfp exe called from IIS to generate PDF file.
>>
>>So REPORT command is useless in webserver programming. VFP does'nt have any
>>web reproting facility.
>>
>>Report errors cause a modal dialog with OK and Help buttons.
>>To close it, run an external process before report command.
>>This process can simulate a enter key press or mouse click to OK button
>>in error dialog.
>
>Andrus,
>
>I agree with you, but perhaps this functionality could be improved in the future version of VFP? May be we also can call Report with some parameters and have complete OOP report writer?
>
>Currently I'm using plain VFP environment, but I found this quite inconvenient and this dialog very user-unfriendly...
>
>BTW, can you expand about using external process to close this dialog automatically? Is there a way to know, that this dialog tried to appear?
>
>Thanks.

I think you can simply stuff a Enter key to windows keyboard buffer.
If error occurs, enter key is consumed by error handler, if not, use
CLEAR TYPEAHEAD after REPORT command.