![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
1) Is there a way for a trigger to know that it is operating against a table or dictionary? I have never needed this before and don't know if it is possible. Cant find anything in the ACCESS() info but thought i would ask. 2) Is there a way to know the process that is causing the change? Is there a 'call stack' which can be interrogated? If it makes a difference this is specifically for CALLX but generically for any of the triggers. the learning never stops thanks dtsig |
#3
| |||
| |||
|
|
Access(11) will NEARLY give you want you want .... you may need to have slightly different versions of trigger for dict/data levels to differentiate dtsig wrote: 1) Is there a way for a trigger to know that it is operating against a table or dictionary? I have never needed this before and don't know if it is possible. Cant find anything in the ACCESS() info but thought i would ask. 2) Is there a way to know the process that is causing the change? Is there a 'call stack' which can be interrogated? If it makes a difference this is specifically for CALLX but generically for any of the triggers. |
#4
| |||
| |||
|
|
1) Is there a way for a trigger to know that it is operating against a table or dictionary? I have never needed this before and don't know if it is possible. Cant find anything in the ACCESS() info but thought i would ask. 2) Is there a way to know the process that is causing the change? Is there a 'call stack' which can be interrogated? If it makes a difference this is specifically for CALLX but generically for any of the triggers. the learning never stops thanks dtsig |
![]() |
| Thread Tools | |
| Display Modes | |
| |