...and some stupid programming!
Here's the situation. This system I work - goes back to the FPD days - although they made it sort of a Windows program - even though its still all @ Say/Gets & Blue screens w/While letters. Anyway - they have this Windows program - that is a true VFP program (although maybe more like FPW - but, whose counting anyway). And, this particular system is purely for reporting and viewing of data. Well, many of the reports are carried over from the older FPD/FPW type system. So - there is this particular reporting screen - with LOTS of criteria (you know - nicely cluttered) - and when you hit OK - its got the code to start generating a report. Some of that code is in this screen. But, the guts of the code is in an external PRG. And, from this screen - the calls are made to Report Form. But, in each of the Report Forms that are called - in the Data Environment - it calls the External PRG program - and does the main gathering of Data. The problem is - and here's the stupid part - there is NO Need to call that external program from within the Data Environment. Instead - that external program should be called FIRST - from within the criteria Screen - RIGHT Before calling the Report Form. And, I made this change for one of the reports Forms. However - this Bloody Screen calls EIGHT Different report forms - based upon the reporting selection criteria. It seems that when you put even 1 stupid line of code into the Data Envrionment (which is what the programmers did here) - it starts up another data session. Problem is - when I run that program (the external PRG) before calling the report - it sets up the Temp cursor and is ready to run the report. But, since the Report Form does this Data Environment thing - it seems to open up ANOTHER Data Session (true - I'm not a super VFP OOP - so, I'm not always familiar with all the basics). And, so - I understand why its doing this. Problem is - in the LAST report form I fixed - I tried taking the code out of Data Environment - both the BeforeOpenTables and CloseTables methods. But, it didn't help. And, with the last report I fixed - I literally created a new Version of the report form - and reimplemented all the content in it from the Old Form. And, that did it. But - that method requires TOO Much work - and I KNOW there must be a Better way! Even if its something like opening the Report form as a DBF type file - and directly editing something to fix my problem. But - I am hoping someone has an easier method. Anyway - thanks in advance - and sorry for such a lengthy e-mail (they especially HATE it when I do that here on the Job!)... Thanks, -K- Developer Waitex Information System, Inc. --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html --- _______________________________________________ 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/289ea162f5642645b5cf64d624c66a1409df1...@us-ny-mail-002.waitex.net ** 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.
