tag:blogger.com,1999:blog-5881807458099247013.post564762937228638037..comments2023-05-27T06:40:42.970-04:00Comments on Cathy Pountney: SET TALK appears to be on when running reports with SP2Cathy Pountneyhttp://www.blogger.com/profile/04600819277331440680noreply@blogger.comBlogger7125tag:blogger.com,1999:blog-5881807458099247013.post-59381571632782089092010-08-18T02:47:41.204-04:002010-08-18T02:47:41.204-04:00Cathy,
Thanks for the post, but it is out of date...Cathy,<br /><br />Thanks for the post, but it is out of date, or something.<br /><br />Following is the code from my version of the:<br /><br />_Reportlistener.LoadReport<br /><br />As you can see, while I have the <br />"THIS.setFRXDataSessionEnvironment()"<br />line, I don't have the other.<br />I tried simply adding set talk off, but this didn't help. Before I spend a bunch of time on this, do you happen to have a solution?<br /><br /><br />===================================<br />THIS.clearErrors()<br /><br />THIS.setFRXDataSessionEnvironment()<br /><br />THIS.resetDataSession()<br />THIS.frxHeaderRecno = -1<br /><br />IF NOT ISNULL(THIS.Successor)<br /> WITH THIS.Successor<br /> .AddProperty("isSuccessor",.T.)<br /> .AddProperty("commandClausesFile",THIS.commandClausesFile )<br /> .PrintJobName = THIS.PrintJobName <br /> .CommandClauses = THIS.CommandClauses<br /> .LoadReport()<br /> ENDWITH<br />ENDIFJaynoreply@blogger.comtag:blogger.com,1999:blog-5881807458099247013.post-48237377015692241662010-05-22T18:12:59.926-04:002010-05-22T18:12:59.926-04:00This comment has been removed by a blog administrator.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-5881807458099247013.post-42445776755684696232009-08-20T14:41:36.973-04:002009-08-20T14:41:36.973-04:00Hi Cathy,
Thanks for replying...
< Why are yo...Hi Cathy,<br /><br />Thanks for replying...<br /><br />< Why are you copying the vcx to your class folder?<br />To avoid dll hell from future updates... I copy all all the classes my applications use into their own class folders and include thwe class folder in the apps path.<br /><br />Now you are the expert here and I'm willing to take any advice that you give... Also, I have both books titled "The Visual FoxPro Report Writer" and "Whats New in 9". I've also read/studied them. The first book has no info about this new object oriented approach, and the later book where Doug presented his material covered it but not in enough detail to start utilizing it past its generic behavior.<br /><br />My fustration with this new report writer is real... I can see and I know from both your presentations at the 2007 SW conference that it is quite capible, but so is the C language, as for me and what I've been able to put together using this new writer, you may as well as give me a cd with the C language and say "it will do it", and ofcourse if you know the C language, it can.<br /><br />I have several what seems to be simple problems to solve and I'm not getting anywhere. Enough crying.......<br /><br />1. I downloaded the latest xsource and fll folder files from CodePlex and extracted them into the xsouce and fcc folders under VFP9. <br />2. I then created new apps from the "ReportBuilder, Output, & Preview" projects and placed the .app files in my projects App filder and pointed to them in my main.prg like this:<br /><br />Set REPORTBEHAVIOR 90<br />_ReportBuilder = '.\Apps\ReportBuilder.app'<br />_ReportOutput = '.\Apps\ReportOutput.app'<br />_ReportPreview = '.\Apps\ReportPreview.app'<br /><br />3. I also copied the report listener vcx from the fcc folder into my projects class folder.<br /><br />Cathy, some of the simple things I need to fix is;<br />1. the 32??? pages to print in the print dialog when there are really only 3. (client complaints) <br />2. How can I tell if the user <br />a) pressed cancel from the preview form, with object type 1<br />b) pressed cancel from the print form, with both object types 0 and/or 1.<br /><br />4. What do I modify, and how do I pipe it all together <br /><br />5. Also, what am I missing here? In the commands;<br /><br />loListener = createobject("MyReportListener")<br />report form MyReport object loListener<br /><br />I read this as loListener as an EMPTY object with no functionality. If so, then what good is it and how can it possible suggest anything to the report engine?<br /><br />6. Samples/examples with remarks are very helpful. Is there any collections of these.<br /><br />Cathy, I believe that once I know where things go and how the engines think, the battle will will be half over.<br /><br />Thanks so much!<br />Stanley BarnettStanley Barnettnoreply@blogger.comtag:blogger.com,1999:blog-5881807458099247013.post-69635542593070280342009-08-18T21:13:05.067-04:002009-08-18T21:13:05.067-04:00Dear Anonymous,
Why are you copying the vcx to yo...Dear Anonymous,<br /><br />Why are you copying the vcx to your class folder? When the reporting engine instantiates a report listener, it does so from the FFC directory ... unless you've customized the report output app and redirected which listeners are instantiated.Cathy Pountneyhttps://www.blogger.com/profile/04600819277331440680noreply@blogger.comtag:blogger.com,1999:blog-5881807458099247013.post-42895526438866663242009-08-18T20:17:00.117-04:002009-08-18T20:17:00.117-04:00Cathy, it doesn't work for me on XPsp3 - VFP9s...Cathy, it doesn't work for me on XPsp3 - VFP9sp2. After making the changes to the vcx, I copied them into my class folder which my app is pointing to. I verified the changes were in the vcx file, and they were. I have a clean VFP9 to sp2 install, skipping sp1. The work around I've had to re-implement is to add "set console off" before the report form and "set console on" afterwards. Also note that using the "NoConsole" keyword to the report form command does not work.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-5881807458099247013.post-64030487388863987232009-07-31T16:29:48.718-04:002009-07-31T16:29:48.718-04:00Very good. I was crazy find for this. thanksVery good. I was crazy find for this. thanksSaulo Morais Larahttps://www.blogger.com/profile/09870107301479185664noreply@blogger.comtag:blogger.com,1999:blog-5881807458099247013.post-28521152362663545652009-04-11T17:00:00.000-04:002009-04-11T17:00:00.000-04:00Thank for sharing this, Cathy! We'll make the move...Thank for sharing this, Cathy! We'll make the move real soon now!Christiannoreply@blogger.com