To have it implemented by the scheduler you'd need to write some code (vb.net or C#). You could probably setup a trigger of some sort on the scheduler logs, though I'm not a SQL expert by any means. Doing so may or may not cause issues, I generally try to tell people not to modify the core tables in any way as that can be a huge problem when you try to upgrade to a newer version of DNN.

---

Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee
Christoc.com Software Solutions DotNetNuke Module Development, Upgrades and consulting.
dnnCHAT.com a chat room for DotNetNuke discussions

Antonio,

I'm trying to setup a system where many portals in a single dnn install will have a links module - which will display links from a SQL table. I need to be able to update all the portals as needed

I figure I can create a list with these 'master links' then write a sproc to look for a links module instance in every portal, delete the existing links, and insert the new links from the list

I'll have many sites based on a template - the teplate will contain a 'links' module instance - I will avoid messing up other links modules by giving the module a unique title