Hi Javier,

I highly suggest utilizing a service-based interface to the DotNetNuke framework using, for example, Michael Washington's IWeb module.  This will make your code much less resistant to future schema changes (database-level manipulation is not a supported use case for DotNetNuke) and probably more straightforward as well.

Hope this helps!

Brandon

Hi Javier,

That's likely the only place you'd need to do an insert, keeping in mind that it might break in future versions (via schema changes including new non-default columns or new foreign keys).  So long as you're prepared for that, I think you're good to go.  You'll also want to be especially careful about how the insert is authorized; you have opened up additional security risk here.

Brandon