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 _____________________________________________________________________
