>>>>>>Ok, after I removed that Print When expression I am now getting an ugly 'syntax error' with no explanation. Why REPORTS are so hard to debug?
>>>>>>
>>>>>>I put a breakpoint into that esppimg program but I still get 'Syntax Error' and it does not go into the program.
>>>>>
>>>>>I hate pictures in report.
>>>>>What this function returns and why you need function?
>>>>
>>>>I give up :(((((((((((( Why would it now return 'Syntax Error' with only 'Ok' and 'Help' buttons? How would I know why does it return syntax error?
>>>
>>>Maybe because it returns empty picture?
>>>Let this function return some external picture and then test it.
>>>Something like:
>>>

>>>LPARAMETERS ....
>>>IF EMPTY(param1)
>>>   RETURN LOADPICTURE("d:\empty.bmp")
>>>ELSE
>>>   * original body of the function
>>>ENDIF
>>>

>>
>>I don't think that's the case. Why I can not even make it to stop to debug this function when I put a breakpoint at the top? And I do call it with the parameters, e.g.
>>
>>esppimg('guests.mug_shot',2)
>>
>>This function can log some info, I can add logging into the top to see if it logs something at least. But I think it's not being called but returns the error right away.
>
>Maybe if you use a listener than you can debug it?

Naomi can debug own function... SUSP

MartinaJ