Hey Dave - thanks for your feedback - sounds similar to Fred's. I'm going to attempt to try it and see if that solves the problem.
-K- -----Original Message----- From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of Dave Crozier Sent: Monday, February 04, 2013 10:30 AM To: profoxt...@leafe.com Subject: RE: MORE Screen Hacking & a Query... Kurt, Off the top of my head, isn't the memo field simply compiled code. Removing it should force a recompilation and apropriate re-constitution of the correct code in the form you are modifying. VFP checks to see that the compiled code matches the source code.... but sometimes gets it wrong, which is when you need to do exactly what I have described... it's the same for .prg files and their associated .fxp files that need to be deleted, hence forcing a re-compilation. I think this is what you are getting at.... Dave C -----Original Message----- From: ProFox [mailto:profox-boun...@leafe.com] On Behalf Of Kurt Sent: 04 February 2013 15:16 To: profox@leafe.com Subject: MORE Screen Hacking & a Query... Hey Folks, I've made a LOT of progress on this Utility I've been working on - to automate conversion of system PRG code to Screens/Forms. However, I've run into a complication that's a bit of a stumper. Just to Prefix the explanation of the problem. To do the Screen Hacking - I create what I call a Base Screen - which has Basic controls in it - including a Container for the creation of required Pop-up windows. I copy that Base Screen to a New screen file - for each program that will be converted. Then I duplicate the basic controls - making copies of the records - to create the new controls on the new screen. I'm now starting to look at implementing Methods - like the Screen Init - in particular, putting into it the Parameters statement from the PRG. I created dummy code - really just Commented code - within the INIT Method in the Base Screen. However, here's the problem. I open up the Base Screen as a DBF file - to look at how that INIT Method is actually implemented. And, of course, I see the Code within the Methods memo field - formatted as a Procedure. No problem there. I got my conversion program to implement that without a problem. The problem lies in the ObjCode memo field. I saw in the Base screen that this ObjCode memo field has cryptically encoded data - lots of strange characters. But, within all those strange characters - I found it showing the word "INIT". So - obviously the Init code is in there. But, how to I properly implement this ObjCode memo field. Since, its definitely related - and, on the new screen I generated - the Methods field looks fine when I open the Screen like a DBF. However, when I open the Screen AS a Screen - and I look at the Init Method - its mostly Garbage! I'm sure those familiar with the intricacies of Screen Hacking know what I am talking about - and, hopefully can point me in the right direction. TIA, Kurt --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html --- [excessive quoting removed by server] _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/B83893490307453589E1AA3ADF1784A2@Programming2 ** 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.
