The phdcc.Data modules are distributed as in a single combined zip file with a dated name such as phdccData080115.zip. Unzip this file first into an empty directory to obtain a README.TXT file, the individual DNN Private Assembly (PA) module zip files, and a copy of the current documentation. Each module filename includes the version, eg phdccDataForm_01_02_03.zip

Only use these modules if your database is SQL Server 2005 or later.

Install the modules in this order:

• Install phdcc.Data.Form to define your tables and forms and get user input
• Install phdcc.Data.View to view results
• Install phdcc.Data.List to view a list of results
• Install phdcc.Data.Search to display a simple search form

To install each phdcc.Data module, login as Host. In the DNN Control Panel, select "Install Additional Modules" then "Install New Module" at the bottom of the page. Click "Browse" and select the required phdcc.Data module PA zip file on your system. Finally click "Install New Module". Have a look through the all the gobble-de-gook output to check for errors - ie anything in red. After you click on "Return", DNN may take some time to return as the whole system is recompiled; if necessary click on another link to wake up the system.

The phdcc.Data modules usually use the DNN conventions for upgrading safely. Follow the same procedure described above to upgrade an existing installation. All existing data will be preserved. If you have customised the layout, then save your changed files before upgrading - see the versions page for more details.
To upgrade from phdcc.Form to phdcc.Data.Form, see here

phdcc.Data.Form

• Import: better error report in Event Viewer
• Admin: option to remove unused (non-standard) strings
• Question param: validation expression
• Question param: read-only
• Question type: make into .ascx user controls???
• Question type: dropdown, dropdownmulti, date, password, other DNN types
• Question type: provide a design-time view to make customisation easier
• DNN profile data types: TrueFalse, Date, DateTime, Country, List, Locale, Page, Region, RichText, TimeZone, Integer, Text, Unknown
• Option to email form results to user if logged on
• Edit form: disable group when question being edited etc
• Results: deliberately not deleted if the associated form is deleted. But how to cull unwanted results?

• Results: Use Javascript to check length of data entered on the fly

• Moderation:
  • Email user that info accepted
  • Un-authorise a resultset
  • Revert to last authorised result
  • Delete whole submission
  • Find deleted users and delete all their submissions
  • Remove unncessary resultsets that do not validate
  • Authorise option: if nothing changed then just set Authorised flag
  • Moderate 'Recordset' form results

• To support a gallery of images for a user (for example) a new form type is needed, 'ProfileList', where a user can have multiple instances of a form for themselves. The initial 'ProfileList' display is a list of their current form instances. There are options to Add/Modify/Delete instances of the actual form.

phdcc.Data.List

• Don't use a SP to do search because all results are already in memory, ie do search by hand in memory
• Use System.Web.Caching.Cache to store phdcc.Data.List.ResultSets.LoadedResultSets

phdcc.Data.Data

• Could provide functionality that supports: foreach( ResultInfo ri in FormX("idForm"))

phdcc.Data.List, phdcc.Data.View, phdcc.Data.Search

• Check XSS susceptability

General

• Reposition as a (simple) online alternative to MS Access:
  • Let user define a (real) table, with correct column type (ie not all results as text)
  • Form editor then builds a form to get input into this table
  • See if it can handle existing simple Access app (eg BDLHS Tithe Map)
  • How does this compare to MS Access's "data access page" feature?