There may be code in the application that uses the " IN " clause already
(DO MyFunc IN Init.prg).
So in addition to searching for the "SET PROC" string, you may want to
search for the " IN <name of main prg>" (where you put in the name of
the prg that you've been reducing).
I think I heard it mentioned that you're in VFP 6, so your searching
options may be limited (if you have VFP9 use the Code References under
Tools). But you could write an app that searches all other PRGs pretty
easy. The Forms would be tougher but you could still just string search
the FPT (or SCX or FRX) files and see if the string is in there. You'd
at least know which Form/VCX/Report, etc has the potential to cause the
problem.
-Charlie
On 4/21/2014 3:14 PM, Fred Taylor wrote:
At the point that it fails, can you put up a messagebox or something that
shows you the value of SET("PROCEDURE") to make sure you haven't got some
code somewhere that's not got the ADDITIVE clause.
Fred
On Mon, Apr 21, 2014 at 11:56 AM, Desmond Lloyd
<[email protected]>wrote:
...
Had a large program file that was generating "program too large" errors
when trying to compile. There is a whole slew of separate procedures and
...
Began to get errors that file could not be found when executing "valid
functions" after certain reads. Solution was to move those back to the
original program file.
...
I can go back to the original code and modify to include the "in" clause.
...
_______________________________________________
Post Messages to: [email protected]
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/[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.
