Frank: I take it that you are working with 7.x. I now store all my EEP with the form as it makes maintenance a lot easier; if you need to call the same EEP from more that one location within the form, then create a Custom Action in the form and you can call it from anywhere within the form without having to duplicate code. To upgrade a form on a production database, simply load the new form into the database even if another user is using the form at the time, the next time the user open the form he will get the new version...piece of cake... As far as testing, TRACE will go one step at the time through the EEPs when they are called, no problem there. On my old applications I used to have hundreds of EEPs that needed to be reloaded when a form was updated; now, every form is self-contained and self documented; when I load the form all the supporting EEPs are loaded with it. Javier,
Javier Valencia, PE President Valencia Technology Group, L.L.C. 14315 S. Twilight Ln, Suite #14 Olathe, Kansas 66062-4578 Office (913)829-0888 Fax (913)649-2904 Cell (913)915-3137 ================================================ Attention: The information contained in this message and or attachments is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from all system and destroy all copies. ====================================================== -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] Behalf Of van der Zwaag, Frank Sent: Tuesday, May 10, 2005 10:47 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Design strategy Hi All, EEPs can be either entered directly in an object or held as an .eep file outside of a form / object. My question: What is the best strategy? Include in the object or keep outside as a file? The advantage of having the eep outside the form is that it can (1) be relatively easily tested or traced, (2) a particular eep can be called by more than one object, (3) maintenance is relatively easy. The disadvantage is that you could potentially end up with many eeps and the whole could potentially become a bit uncontrollable and therefore unsustainable. The lesser components you have in a software bundle, the lesser the changes of one going missing or being inadvertently changed. On the other hand, does including the eep in the object make software upgrades more complicated? That is, does it require to unload the form from the development database and reload it at the client production database? Secondly, how easy is it to trace eeps that are embedded in the objects? Can I get some feedback on what you see as the best design / develop strategy? Thanks Frank van der Zwaag ____________________________________________________________________ CAUTION - This message may contain privileged and confidential information intended only for the use of the addressee named above. If you are not the intended recipient of this message you are hereby notified that any use, dissemination, distribution or reproduction of this message is prohibited. If you have received this message in error please notify Air New Zealand immediately. Any views expressed in this message are those of the individual sender and may not necessarily reflect the views of Air New Zealand. _____________________________________________________________________ For more information on the Air New Zealand Group, visit us online at http://www.airnewzealand.com _____________________________________________________________________
