[RBASE-L] - Re: v9.x: Custom Form Actions vs EEPs

[Doug Hamilton]

SFWPOH! I forgot that CFAs could be called from another form. I store RUN SELECTS in an InternalCode table cuz they could be called from anywhere. So compare CFA vs RunSel: RunSel: If you're in form designer, you don't need to close the form and open MenuForm to edit (due to poor planning ;) or create a "global" CFA Portability to a new db - toss-up?  Generic MainMenu with CFAs vs unloading InternalCode table & importing into new database. Incremental updates from test db to production: Cut & Paste for both? Security against unauthorized editing and prying eyes?  Probably CFA. more...? Doug jan johansen wrote: Bruce,   My vote is for Custom Form Actions. They become part of the application and can be called  from elsewhere like PROPERTY RBASE_FORM_ACTION MyMenuForm|CalledFormAction ' ' note : your main menu form would need the componentid MyMenuForm   Jan     -----Original Message----- From: "Bruce Chitiea" <me...@safesectors.com> To: rbase-l@rbase.com (RBASE-L Mailing List) Date: Tue, 25 Jan 2011 07:21:04 -0700 Subject: [RBASE-L] - v9.x: Custom Form Actions vs EEPs v9.x developers: When creating new forms, do you prefer to create: a) Individual EEPs, or; b) Custom Form Actions? Just wondering. bruce chitiea safesectors inc.