Thanks Frank - I'll have to give that a shot on Monday. The last thing I looked at was the Screen itself - which said it had a Private Data Session. I didn't notice this setting before in the REport Form - so, I will have to see if I can find it - and test it out.
Thanks again, -K- On 11/13/2010 6:45 AM, Frank Cazabon wrote: > Kurt, > > my guess (admittedly from only skimming your messages) is that the > reports are set to run in their own datasession. Open one of the > problem reports and then check if the Report | Private Data Session menu > option is selected. If it is, then that is probably your problem. > > 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 12/11/2010 06:41 PM, Kurt Wendt wrote: >> It HAS to be a DataSession issue. Again - I just did it to ANOTHER of >> the reports - ReBuilt it (create an Empty form - incl Summary section - >> and the Grouping - made all sections of it the same height - the grabbed >> ALL the content from the Old version - and inserted into NEW version) - >> and now the report Prints! >> >> The only difference - is that the OLD one has STUFF in the Data Env.! >> And - I just can NOT figure how to turn that stuff off! Removing the >> code in the TWO Methods I mentioned previously - did NOT fix the >> problem. >> >> Anyway - at this point - it looks like I just have to tediously Re-Build >> each of the reports - using the method I mentioned above... >> >> -K- >> >> -----Original Message----- >> From: [email protected] [mailto:[email protected]] >> On Behalf Of Tracy Pearson >> Sent: Friday, November 12, 2010 5:16 PM >> >> Kurt Wendt wrote on 2010-11-12: >>> Basically - yes. >>> >>> Previously - for the other report form that I fixed - and I was >>> stepping thru some code. I found that the data Did get created - this >>> main Cursor (or maybe it was a DBF) - but - the report form would >>> change to a New Data Session - and therefore could NOT see the data. >>> >>> And - I think it TOTALLY has to do with the stupid coding - a single >>> call to an external program being placed in the BeforeOpenTables >> Method. >>> If I rebuild the report - and do NOT do any Data Env coding - the >>> problem goes away. I just don't' want to have to Re-Build 7 more >>> reports, since the rebuilding tends to be very tedious! >>> >>> -K- >> Kurt, >> >> Just to clarify, SET("DATASESSION") changes and not just switched to a >> different ALIAS() >> >> Tracy Pearson > _______________________________________________ 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.
