<< 1. I know its old school thinking to put routines in compiled application files and the current strategy is to incorporate them into forms and reports instead. Is there a big performance difference in calling to an application vs. within the form? I know its old school, but I am still a little leary of relying on passwords to protect my programming. >>
There is some different in performance -- you'll have to test under your particular conditions to find out how much difference. << 2. Say I go out of my comfort zone and write the applicaitons within a form/report. Is there any way to call a procedure from another form/report? In the old way, I would name a procedure in a compiled application, then call it from wherever I needed it to run. I just hate to repeat code if not necessary, especially if I have to change it at some point! >> Here are the rules that I follow: 1. Code called from one and one place only in a form, and having to do with user interface issues only, is placed in the appropriate EEP. 2. Code called from _different_ places in _the same_ form is placed in a Form Action and called from EEPs. 3. Code called from _different_ forms or from forms and other locations is placed in a codelocked APX file or a stored procedure. Under no circumstances should you repeat the same code in two different places in your application. -- Larry
