Albert, I am curious where you found this tidbit of info in the documentation.
I was under the impression that Triggers were not supposed to RETURN values since They are automatically called and have no way for the user to interact with them after they complete execution. Jim Bentley American Celiac Society [email protected] tel: 1-504-737-3293 ----- Original Message ---- From: Albert Berry <[email protected]> To: RBASE-L Mailing List <[email protected]> Sent: Thu, January 14, 2010 10:34:19 AM Subject: [RBASE-L] - Re: date tracking question Hi, all. The system expects the trigger to return a value to a calling procedure. Zero is as good as anything. Albert [email protected] wrote: > Dennis: I actually have no clue what the RETURN 0 is for. > This code is in my notes document, I've never had a reason to > use it yet, so this was just a copy and paste of someone else's > suggestion. I don't think I've ever used RETURN 0. > > Karen > > >> Thanks, >> >> I’ve got a demo running nicely, thanks to you and Emmitt. >> >> What is the 0 after your returns? >> >> >> >> >> *From:* [email protected] [mailto:[email protected]] *On Behalf Of >> *[email protected] >> *Sent:* Wednesday, January 13, 2010 4:22 PM >> *To:* RBASE-L Mailing List >> *Subject:* [RBASE-L] - Re: date tracking question >> >> >> >> >> I think a variable is the ONLY way. Here's example code: >> >> SET VAR trigger_executed INTEGER >> IF trigger_executed = 1 THEN >> CLEAR VAR trigger_executed >> RETURN 0 >> ENDIF >> ... {body of trigger} >> SET VAR trigger_executed INTEGER = 1 >> RETURN 0 >> >> >> >
