CFA stands for Custom Form Action. That's the code that you store directly in the form itself (Layout / Custom Form Action). That way you can "call" this code from multiple places inside the same form.
What Bob did is to instead store the code inside an RBaset able, in a varchra column, and call it using "run select". This also allows you to call the code from multiple places. So in his case, the program code is identical, he's just storing it in a table rather than inside the form. Can't say I know what would make the difference. Karen -----Original Message----- From: Dan Goldberg <[email protected]> To: karentellef <[email protected]> Sent: Tue, Aug 25, 2015 8:27 am Subject: [RBASE-L] - Re: Button EEP versus Timer EEP Is a CFA a compiled form application? What was the property command? Just want to make sure I note this in the future. Thx Dan Goldberg From: [email protected] [mailto:[email protected]] On Behalf Of Karen Tellef Sent: Tuesday, August 25, 2015 5:57 AM To: Dan Goldberg Subject: [RBASE-L] - Re: Button EEP versus Timer EEP Big High Five from over here!!! Glad it worked! Karen -----Original Message----- From: ttc.inc <[email protected]> To: karentellef <[email protected]> Sent: Tue, Aug 25, 2015 6:53 am Subject: [RBASE-L] - Re: Button EEP versus Timer EEP I changed the code from a CFA to a Run Select and everything ran perfectly last night. I did a cut and paste of the code into the VarChar column, so there were no changes in the operating code at all. Replaced the Property command with a Run Select and this morning all was good. Not sure what the difference is. I have in the past and have now, other apps that use the form timer eep and CFA,s and they do not seem to have any issue. However, those CFA's have 1/4 the lines of code and no Delcare / While statements. Perhaps a connection? Truthfully, I assumed that a CFA was pretty much a Run Select command just build into the form designer. Thanks to all who submitted ideas. -Bob From: "MikeB" <[email protected]> To: "ttc inc" <[email protected]> Sent: Monday, August 24, 2015 2:03:19 PM Subject: [RBASE-L] - Re: Button EEP versus Timer EEP Let's wait to see what happens with the Run Select before jumping out of the boat. > -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf Of Karen > Tellef > Sent: Monday, August 24, 2015 2:10 PM > To: [email protected] > Subject: [RBASE-L] - Re: Button EEP versus Timer EEP > > Javier: I've seen Bob's app before, and it's a cool front-end type of > form with lots of data for the users to see. The timer updates some of > the data on the form. > Let me think, if a scheduled task ran an "outside" RBase program, I > guess it's possible that that program could dump the display data into > a lookup type of table, and could still have a timer on the form that > would gather and recalc the > display. The form could have a "date last ran" / "date next run" so > the user has > some feedback on the process. A bit of work, but it would take the > form out of the equation, wouldn't it? > > > Karen > >
