Hi Bob,
They can be quite useful. One mistake that is easy to make if you do not
think it through is to create an endless loop. Do not make a update trigger
that changes something in the table that triggered the update. An example of
this would be to update a table with the userid of the last person that made
changes to the table. The trigger update runs the procedure to update the
table which fires the trigger and so on. In this case you need to create a
seperate table that links to the row that was updated and put the userid and
date/time or whatever in the seperate table.
Procedures work really well in reports for doing complicated computations to
get a variable to display properly. In some cases it may be impossible to do
this type of computation in a regular report.
There were a few problems but they have been fixed as the Razzak stated in
his post. Have fun! They are cool to work with.
Best regards,
Mike Young
On Fri, 1 Jun 2001 19:56:44 -0400, Bob Powell wrote:
>Hello Everyone,
>
> I'm am currently involved in programming a
>centralized database attempting to adhere to as many of the
>relational theories as possible. Truly attempting to
>design this beast as close to the conceptual design as
>well. This will of course require the use of triggers and
>stored procedures throughout the implementation.
>
> What I am wondering is how many of you have used
>the triggers and stored procedures in R:Base? What has
>your experience been with them? Please feel free to offer
>any other information that will be helpful to me about
>them. Thanks in advance to all.
>
>
>----------------------
>Bob Powell
>The Hotchkiss School
>Lakeville, Connecticut
>Systems Administrator
>[EMAIL PROTECTED]
>
