The repro was what I could come up with based on observations in an actual VFP9 application I am working on. I have no clue how to simulate a "TLF" application under design time conditions to accurately repro this. So I tried to come up with demo code that closely emulates the condition I found under runtime. This app definitely is not designed the way my repro code is and none of my forms that call these types of reports are modal. But it at least reproduced my observation.

The key part of the repro code was that if you SET REPORTBEHAVIOR to 90 and do not change REPORT FORM commands that do work in VFP8 in TLFs, the new toolbar will not be accesssible. I just wanted to either get set straight or find out if this was an actual problem. I think I fall into the former category.

The "so modal" was a lame attempt at humor to beg the question "How modal is it". :)

Thanks for setting me straight.

>Hi Mark
>
>---
>the report is so modal even the report preview toolbar is not accessible
>---
>
>You're not exactly doing anything wrong, although you certainly did over-complicate the repro quite a bit <s>. You don't need an EXE or all that overhead to see this, it doesn't require runtime conditions.
>
>The issue here is not so much that the "report is so modal" (whatever that means <g>) but that the report preview is a true FoxPro form now, and the report toolbar is a user-toolbar.
>
>Those two facts, plus READ EVENTS and the fact that you called the report from the button of a modal form, is going to force certain FoxPro-standard behavior. Granted this behavior is different from the native preview [SET REPORTB 80], and this difference is acknowledged in the docs. Of course we will certainly tune it further (or you can!) if we find a way.
>
>But it doesn't mean that the toolbar as-delivered is inaccessible for top level forms <s>.
>
>To use the toolbar, you can adjust your repro program (and your reporting style for top form apps) by replacing the button code with the following. Yes, NOWAIT means that the report is not modal any more (the report preview form will be called with .Show() instead of .Show(1)). But you will definitely see that the report preview toolbar can function properly in a top form app, it just follows the same rules as other parts of your app now.
>
>

>
>         PROCEDURE cmdReport.Click
>            REPORT FORM RepoDemo TO PRINTER PROMPT PREVIEW  NOWAIT
>            RELEASE THISFORM
>         ENDPROC
>
>

>
>... this takes you out of the modal form and back to the "frame" of your topform app, which is a safer place for the report preview to be.
>
>People who write VFP top form apps have to juggle this type of thing all the time, when they evaluate how to use modality, child forms, and toolbars; now reports have just come to the party.
>
>Because of the way new-style preview works by default -- and I don't think it necessarily works this way in the public beta, even in the component refresh, in case anybody reading this and trying it out scratches his/her head trying to reproduce what I'm saying -- the NOWAIT preview is going to be re-used if it's called more than once; there isn't a danger of seeing tons of NOWAIT previews hanging around. I guess this makes it "sort-of modal" instead of "so modal" .
>
>HTH,
>
>>L<

Mark McCasland
Midlothian, TX USA