Steve: EEPs are command files. They can be blocks (or parts of blocks) in compiled apps.
I don't think speed will be an issue. We have had some very slow forms that have been used, modified, optimized, everything I could think of, for years. In Windows R:Base, they are much faster. Jim Blackburn Kodiak "J. Stephen Wills" wrote: > > Although I'm using RB regularly for DB stuff, it's been a while since I've > done app-dev, so I have a Q about EEP's. I'm working on a high-volume, > high-speed data-entry app and I'll need to be using EEP's w/forms. I seem > to recall (fm the old M'rim days) having read somewhere comments to the > effect that where an EEP was stored could impact the speed of its execution. > If I recall, I formerly created/tested the code in RBEdit and, when I was > satisfied that it was (sufficiently) robust, I copied-n-pasted it into the > form, whether field settings or table settings, as appropriate. > > IOW, should it be located in the form or should it be located in a command > file? > > TIA, > Steve in Memphis > > ================================================ > TO SEE MESSAGE POSTING GUIDELINES: > Send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: INTRO rbase-l > ================================================ > TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: UNSUBSCRIBE rbase-l > ================================================ > TO SEARCH ARCHIVES: > http://www.mail-archive.com/rbase-l%40sonetmail.com/ ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/
