Most modules store configuration information as string key/value pairs in either the DNN ModuleSettings or TabModuleSettings tables and retrieve them from the Settings hashtable available in both your module controls which will inherit from DotNetNuke.Entities.Modules.PortalModuleBase or in the Settings.ascx control which will inherit from DotNetNuke.Entities.Modules.ModuleSettingsBase. Settings stored in the ModuleSettings table will be be the same for all modules having the same ModuleId - including those placed on a page as a clone copy with Add Existing Module or those having the Show on All Pages box checked in their configuration. TabModuleSettings are unique to the module instance on a page - even if the module is a clone.

Michael Washington has a very brief tutorial on Settings and Personalization as well as several example modules at the following site: http://www.adefwebserver.com/DotNetNukeHELP/. A look at the source code of nearly any module will give many more examples of storing and retrieving module settings.

Unless the module requires a very few number of settings, I generally create a configuration class which is responsible for loading/updating the stored settings and exposing them to the individual module controls as strongly typed properties. If the settings are very numerous or if some settings would require storage in long nvarchar fields in the database I prefer to create my own custom table with columns of the appropriate data type for storing the settings and again create a configuration class for loading/updating them.

---

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