Hi,

I have added a SQL Server trigger on the Skins table. When I modify a record in the Skins table through Enterprise manager the trigger fires perfectly. However, when I make a change to the Skins table through DNN (Admin Settings) the data physically changes in the table but the trigger isn't getting fired.

Anyone got any suggestions...?

Personally I am not sure what the issue might be but I will caution you that adding triggers to core data tables is NOT a good idea...

---

-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.


Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services

From version to version of DNN there is never any hard fast rule that the makeup or structure of any CORE table will remain the same.

If you make changes to the core in your own module - you may find that the functionality you require is not longer there in the table you
messed with.

Also - depending on the changes you make - you may actually break future updates - since in many cases upgrade scripts tend to
disable triggers etc before running - then recreate them after the event

Westa