>>
>> >>I have finally gotten Foxfire! to work for me the way I want it to with
>> one exception- when I call the request manager from within my app, it likes
>> to open in/under the Visual Foxpro main window, instead of my main window.
>> Is there a way to modify this behavior? As far as I can see, this issue
>> isn't addressed in the documentation.
>> >
>> >you got it to work? congrats -- we've given up on running it from within
>> our app. users can run it separately or use another report generator...
>>
>> What sort of problems are you having/did you have? I have not completely
>> integrated it yet, just from a couple of places in the app. I plan on
>> calling it from about 10-15 different places- some just printing a report
>> and returning control, and some opening the request manager and allowing
>> the user to choose a report to run. So far, I have been able to get it to
>> do generally what I want... but it looks pretty goofy when the Foxpro
>> window jumps out and my form disappears into the background. Yours is the
>> first complaint I've heard about difficulty with Foxfire, you've got me a
>> little nervous now... anybody else?
>
>I've used it a number of times, and have had to change virtually none of
>the source code. This is using either version 2.x or 3.x of Foxfire!.
>
>But then I've only called it from within full-blown FoxPro applications
>with multiple forms, not from single-form applications. I can see how
>it would be difficult to work with in single-form applications. (if
>used in a single-form-that-does-everything application, you will have
>significantly better results if you call Foxfire! as an entirely
>separate application).
>
>/Paul

I'm not sure what you mean by single-form applications. My app uses a main form, but this is by no means the only form in the app. (About 35 forms are contained within the main form.) Some of the calls are being made through menu procedures, and some through buttons on various forms, but either way, Foxfire wants to run in the Visual Foxpro window, and not mine. Moving the main window off screen or saying _screen.visible = .F. therefore causes the obvious side-effect of also hiding Foxfire!. What to do?