>>I also found that the report used the report's variable in the report footer. This variable was not set to be released after report. I am wondering if I can try adding release this variable in the form's code, will it help or not.
>>
>>Thanks in advance.
>
>I lived situation like you before and it made me mad... :)
>
>Prepare all pictures before printing, put all in a table. Each record for one page. create a group per page. print picture at the summary band of group. Or find another way but prepare pictures before printing and put all of these "pictures" or "pictures file names/path+file names" in a table and print them. This worked for me...

This sounds like a lot of work :(

So far I found that if we use this Print When expression SigId != 0, then all is well. The problem only shows its ugly face when we're using Report's variable and in the Print When condition using ! empty(cSigFile).

I see two possible solutions:

1. Update layouts for the clients to not use this Print When expression

2. Change code that prints the report to generate copy of the report (in the temp folder the copy of FRX/FRT files and update SupExpr on the fly).

I prefer the first solution, but it will make a lot of work for our client service people.