I am starting a new thread because the other one was long. The trigger names (that are the same as the table name) is fixed. The problem when attempting to double click the trigger still exists (Nothing comes up). If I search and find that trigger and double click it I get Invalid SQL, if I use Monitor that’s all it says as well.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| SQL Navigator 6.2.1 DB Explorer and triggers | 1 | 966 | January 7, 2010 | |
| Triggers | 7 | 2204 | March 22, 2012 | |
| Someone in Quest hates triggers! (this is my 4th post about them!) | 1 | 797 | February 18, 2007 | |
| Trigger Editor | 2 | 1111 | November 24, 2010 | |
| [17.0.41] Full qualified trigger name when loading from the schema browser | 3 | 387 | May 5, 2023 |