You will definitely need UserID and also an ItemID (for multiple To Do's belonging to the same user) in your ToDoList table. You should also include either a ModuleID or PortalID column as explained below:

1) If you plan to have multiple ToDoList modules with different item data for each module you will need to add a ModuleID column to the table with a foreign relationship and cascade delete going back to the core Modules table. This will confine data to the particular module instance and allow the core API to delete the ToDoList table data when a particular module is deleted and removed from the recycle bin.

2) On the other hand, if the same ToDoList data is to be shared across all ToDoList modules in the portal you should add a PortalID column with a foreign key relationship back to the core Portals table. This will confine data to the portal on which the module(s) are installed and cause deletion of the ToDoList table data when a particular portal is deleted.

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner

If you want to show aggregate list of the portal then you have to use PortalId and if you want to show list module wise then use ModuleId

Regards 

---

Leo TechnoSoft Pvt.Ltd - The Biggest DotNetNuke Development Team