Visual FoxPro in general Re: Effect of Screen = Off in config.fpw Thread #481661 Message #481760
From 04/03/2001 16:00:02
Tobey Miller #030670
Meridian Information Systems
Boca Raton, Florida
To 03/03/2001 19:35:46
Barbara Paltiel #008490
Paltiel Inc.
Burlingame, California

Yes, my application runs in a Top Level Form and I have the READ EVENTS, but your questions pointed me to a solution. My problem was this: I had purchased the FoxFire! report writer software and had added a command button to my original application that allowed my user to go into Foxfire. (Aside: While my application runs in a top level form and has a read events, Foxfire does not). A couple of screens in the Foxfire code were not yet fully converted into VFP and were retrofitted by the Foxfire people (still had Define Windows). In the executable version of my application, these screens behaved badly and were unusable by end users. I notified Foxfire of the problem last fall and they said they'd have a fix in the form of an upgrade by January. Last week they informed me that the upgrade is not ready and gave no indication of when it would be ready. So...with users breathing down my neck I set out to fix the problem myself.

I discovered that I could solve the problem by imposing a dummy form before calling the Foxfire software. This worked great as long as I was running from within VFP (with the SCREEN=OFF command in the config.fpw) but I couldn't use it in my executable because putting SCREEN=OFF in the config.fpw caused the whole application to "hide". Your reference to the _Screen object gave me the clue I needed. Before calling the Foxfire software, I added a _SCREEN.VISIBLE = .T. and a _SCREEN.SHOW(). This allows Foxfire (which runs in Screen) to have its main screen visible and active, which is what it needed!

Thanks again for your help.