General information
Category:
Coding, syntax & commands
AFAIK, this is illegal in a trigger. I do something similar in the routine that runs on the save button click. IMO your original place was the right one.
>I added a field to a table called 'fcmodby'. Wanted to use this as a field to log who changed the record. I created a stored procedure that populated this field. The stored procedure was called from the Update trigger of the table. I'm using BUFFERING of 5, private datasession. When I made a change to the table, the stored procedure called correctly but failed with a "cannot update cursor" error. The record is locked (because of the tableupdate() in this case) when the stored procedure is called. Wouldn't I still be able to modify a field within the same record if I was the one that initiated the lock?
>
>I had orignally just used this same code in the Save event of my form class. Then I moved it to a stored procedure instead to be called from my tables that needed it. It may make more sense to move it back to the Save event, but despite that I wanted to know what was at work here.
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only