Is one of the messages about GFXLISTENER, or something like that? If
so, that is a bug in the ReportOutput.app in VFP 9 SP2 and this is the fix:
Get the VFPSource code, open the Reportoutput.pjx, modify the LoadReport
method of the fxListener class in Listener.vcx and add this code as the
first thing in that method:
local m.liSession
m.liSession = SET("Datasession")
this.SetFRXDataSessionEnvironment()
set datasession to m.liSession
rebuild the application and use this new one instead.
Frank.
Frank Cazabon
Samaan Systems Ltd. - Developing Solutions
www.SamaanSystems.com
Referrals are important to us.
If you know of anyone who would benefit from our services, please contact me.
We would appreciate the opportunity to work with them.
On 04/08/2010 02:22 AM, Alan Bain wrote:
> Hi all,
>
> I am trying to move to the vfp9 report listener and having something
> happen that I can't track down. I set reportbehavior to 90 and have
> set talk off. When I run the form in IDE mode and preview the report
> it works as expected. However when I run the report in my app and
> preview I get lots of memory variables painted in the window which
> looks ugly and messes up all the controls on the screen. It acts like
> set talk is on, yet when I put a few wait windows set("talk") it
> always come back off. What else could be causing this behavior?
>
[excessive quoting removed by server]
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
