I have a table with a trigger on it for when a record is deleted a portion of that record goes to another table. Is it possible to background the triggers action so that the foreground application does not have to wait on it.
Since the data is deleted once the trigger has completed, and in some instances you can modify the data that will be acted upon, Texis does need to wait for the action to complete. If you are doing something complex then you could do a quick copy of the data, launch a background process, and return.