Rodney Joyce wrote The Event module has been designed to allow easy customization and localization of fieldnames and pick list values by taking advantage of the latest DotNetNuke architecture (Localization and Lists). This means that the process is standard for all DotNetNuke modules and allows users and developers to take advantage of the framework without having to reinvent the wheel. Customizing Field Values All field values use the localization architecture: a resource key is used in the .aspx form, and the actually value it retrieved from the .resx files for the corresponding page. The .resx files are stored in the \App_LocalResources under the module folder name under DesktopModules, and there is one for each .aspx file that is using localization. Before you start editing values, it is essential that you understand how localization and Cultures work. For more information read the DotNetNuke Localization.doc document in the Documents Folder of your DNN installation. For example, if the FieldName was "DressCode", and you wanted to display "Atire" on the .aspx page, you can open the EventEdit.ascx.resx page in the editor of your choice, and find the corresponding resource key as specified in the .aspx page (by opening the .aspx page and searching for "DressCode"). You can then edit the value to the value of your choice. Save the file and refresh the page. Bear in mind that if you change the values for a culture, then all portals that display the values in this culture will use these files. Changing List values The dropdown lists use the core DNN functionality to follow current DNN standards and allow a consistent UI for customization and flexibility. Please consult the core DNN online help for information on changing List values (Smart-Thinker module Lists always start with Smart-Thinker). You can add values and edit existing values for lists used in any Smart-Thinker module, but it is worth noting that this complicates upgrades and should be done with care. Do not change the value of the list item, only the description. The current DNN architecture has List functionality at Host level, which means that the lists will be the same for all portals. I believe this to be a major limitation and have requested the Core DNN team to consider moving Lists functionality to Portal level. Please raise this with them if you agree to speed up this process. Another limitation is that List values cannot be localized until the Core handle non-static localization (check www.dotnetnuke.com for the Roadmap and updates). The Core Team do a great job and are not paid for their work, so please bear this in mind when requesting these types of functionality updates.

Ok, I tried to read this and it is WAY too ambiguous to be a timely, adequate response and solution.  I need to add new categories and cannot find where to do that.  I need to know how to do that, again, pretty STAT.  PLEASE help me to do this once as your module is the only one I am having issues with in this manor and need to release this system today.

PLEASE HELP!