David, Thanks for joining the discussion!
First of all, I'm not worried about wrapping the wrapping the EXECSCRIPT, EVAL, or COMPILE commands as these can easily be wrapped with a simple function that invokes a VFPPLUS.APP preprocessor. Secondly, if you're *JUST* dealing with PRG code, then a non-hook solution works OK (not great, but managable). The problem is you can't put VFP++ code in any of the VFP designer code snippets because all the VFP designers automatically compile snippet code when a snippet is saved. There is no way to turn this off. This means that you can not use VFP++ syntax in the form, class, report, and menu designers :( Do you have any ideas on a work around? Malcolm _______________________________________________ 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 ** 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.
