I'm not certain if there is a "best" way to handle this, but I wish to
display a "please wait" dialog on the screen before a report is fully
rendered. By fully rendered, I mean that the first page of the report
appears on the screen. It appears as if all of a report's events are
triggered long before the first page of the report actually appears.

Does anyone have an optimal way of handling this?

Thanks.

Vincent

On Aug 5, 12:42*pm, Vincent <animedrea... (AT) verizon (DOT) net> wrote:
Answered my own question...I can keep the please wait window open and
close it after the call to docmd.openreport()...

Seems to be working well.

Vincent

On Aug 5, 12:48*pm, Vincent <animedrea... (AT) verizon (DOT) net> wrote:
Actually, this is not working as intended....

The please wait window launches after which a "blank" report area
opens as the report is generating. After this "blank" report area
opens, my please wait window disappears (but it is still loaded). Is
there any way to prevent the please wait window from disappearing?

Vincent

Vincent wrote:
I would be under the impression that a msgbox, being a dialog form,
wouldn't process much of anything until there was an click action done
on the messagebox.

Are you updating records when you run the report? What are you
attempting to stop? Basically, I view a report as a snapshot of data at
this particular second.

I suppose you could run thru the report and set a flag...If false don't
print, if true then print. See help topics on NextRecord, PrintSection,
MoveLayout.

Build a form and set it as popup.

docmd.OpenForm "nice little form with please wait message"
doevents
docmd.OpenReport "myReport",acViewPreview
docmd.Close acform "nice little form with please wait message"

Albert K.

On Aug 5, 8:36*pm, "Albert D. Kallal" <PleaseNOOOsPAMmkal... (AT) msn (DOT) com>
wrote:
The prize goes to Albert K.

Thanks--this works great!

Vincent

"Albert D. Kallal" <PleaseNOOOsPAMmkallal (AT) msn (DOT) com> wrote in
news:GNI6o.51605$3%3.5839 (AT) newsfe23 (DOT) iad:

How does this interact with "show windows in TaskBar"?

Also, while a popup stays on top, it doesn't pause code.

Last of all, since DoCmd.OpenReport runs asynchronously, the dialog
will close just as soon as the report starts opening, not after the
preview finishes painting the screen.

I'm not sure it's entirely possible to address this. Perhaps the
report's Activate event would do the trick, but I don't know when it
happens when there's a PopUp form open, nor if it happens as soon as
the preview begins or only when the preview is finished.

If that doesn't work, maybe the OnPrint event of the report's page
footer, but I don't know for certain that this fires in print
preview (I'm pretty sure it does). You can't use the report's footer
(if there is one), because it doesn't fire until the preview
displays it.

I think I would likely go back and examine what problem I'm trying
to solve here. Why does the original poster think the users needs a
PLEASE WAIT notification at all? The hourglass mouse pointer occurs
-- isn't that sufficient?

--
David W. Fenton http://www.dfenton.com/
contact via website only http://www.dfenton.com/DFA/

David W. Fenton wrote:

a message to display while the report ran. Similar to a "wait window"
in FoxPro. For most of us reports appear almost instantly. I'm going
to assume the report the OP was discussing is sluggish and needs an
substantial amount of time to process.

Salad <salad (AT) oilandvinegar (DOT) com> wrote in
news:hv-dnRk84Ii61sHRnZ2dnUVZ_qqdnZ2d (AT) earthlink (DOT) com:

And? I have plenty of reports like that. I was just troubleshooting
one last week that takes about 2 minutes for the first page to come
up and 15 minutes to preview the last page. The hourglass is fine,
seems to me, so I'm not sure what is gained with a PLEASE WAIT
notification -- that's precisely what the hourglass means across all
Windows apps, i.e., "I'm busy now, but working on it."

--
David W. Fenton http://www.dfenton.com/
contact via website only http://www.dfenton.com/DFA/

On 07/08/2010 22:12:43, "David W. Fenton" wrote:
I also have slow reports with a lot of VBA running behind the queries. The
user wants to be sure something is happenining and the application has not
crashed or gone ito an endless loop. Hourglass will certainly not show a
problem with and ensless loop, but what about a crash? Is there a better way
of showing the program is running than SysCmd(acSysCmdSetStatus and say
someone's name?

Phil