>Hi Nadya,
>
>I thought Set message might be scoped to the data session so I tried to place a set message in the open tables method of the report form and it prevented message in preview from the report designer, but nothing that I tried worked with the report preview screen from report form promopt command. Set message prevented messages on changing work areas and calling other programs but the report preview window did still displayed the annoying table info. I did not try calling forms. Does it also do this from forms?
>
>As a workaround, you might want to set the status bar off before calling the report form and reset it afterwards. You might also want to try setting up a progress bar with no bar or maybe display an animation control and move it to the status bar to cover the offending area. I'm sure you have probably already tried these but just in case...

Hi Elmer,

I guess, I just give up. Nobody complained so far. I'm just being paranoid :) Besides, I almost got rid of them. For example, if I need to print a report to a temp file to produce number of pages, I just lock the screen with API functions. It's not a perfect solution. For example, once I had an error, but since I locked the screen, Error Message could not come up, and my only final choice was to re-boot the machine...