Actually - as I mentioned before - there is no inclusion within a Project - as we only use a Proj for the main EXE we build for them (with the main Proc file, the main screen, menu and such) where as ALL the rest of the system is separate FXP's we load up to the clients.
Anyway - suffice it to say - I did the setting Proc & Release to deal with my issue - and that worked fine... -K- -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Jeff Johnson Sent: Wednesday, April 28, 2010 12:51 PM To: [email protected] Subject: Re: Calling a Procedure in ANOTHER Program... I use this technique all the time. I keep a procedure file external so I can change it on the fly. I let it build into the project and then right click on it in the project and click on "exclude." Jeff Jeff Johnson [email protected] SanDC, Inc. 623-582-0323 Fax 623-869-0675 http://www.VetsFindingVets.org On 4/28/2010 9:01 AM, Tracy Pearson wrote: > Kurt Wendt wrote on 2010-04-28: >> Yes - Tracy - I guess you are right. I wasn't seeing the obvious. I >> will go with that approach. >> >> And - John - thanks for you additional follow-up. >> >> -K- >> >> > > Kurt, > > If you use the SET PROCEDURE, it might add it to your project when you > compile. > To prevent this use macro substitution. > > Tracy Pearson > PowerChurch Software > > > > [excessive quoting removed by server] _______________________________________________ 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/289ea162f5642645b5cf64d624c66a14071a1...@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.
