Last post Feb 28, 2006 04:40 PM by codegalaxy
Feb 23, 2006 08:04 PM|codegalaxy|LINK
Okay here is the story our agency does tons of conferences put on at various times throughout the year. Some are for teachers some are for teahers and others and some are for anybody who has an interest in education. In the past we have created individual
registration forms for each conference poring into Access or MSSQL databases. This is a real pain in the a** it seems like I do nothing but maintain different registration forms on a ton of different urls.
I want to use DNN to create a registration portal where a conference can be added in some sort of ADMIN panel and then people can come and register with the portal get emails about the conferences posted or just register with a conference without registering
with the portal.
Each conference needs to capture a variety of information about the people who register. Seemingly each conference is different. What would be a good way to provide some sort of configurable form that could be saved to be used later the next year or at
another event if it requires the same info.
I would appreciate any good ideas
Feb 24, 2006 10:21 AM|RLyda|LINK
Feb 24, 2006 10:44 AM|codegalaxy|LINK
well sometime by the end of summer - heres a thought from one of my coworkers but not quite sure how to save after you build the information form.
Each informational element would be like a sub module in the form - for example contact information (name, address, phone, zip, email) would be built as a user control and could be added to each form that needed it - the thing would be to build an interface
(I guess really since its a control just public properies) and allow it to be added to a form
But the saving the input that would be the problem - maybe some sort of serialization or xml type ? What might be easiest on this?
Feb 24, 2006 02:35 PM|RLyda|LINK
We have what we call "Misc Data" structures. For storage, it boils down to three tables: Definitions, Lists, and Values. Definitions is exactly like it sounds: IDs, prompts, tooltips, RegEx for validation, controltype to invoke, ParentID, etc... By
that last item you see that this allows a multi-level usage.
For display my object maps a ParentID to a UI host (such as a panel or frame). Then the object loops through the list of child elements and adds controls as necessary... Obviously some controltypes need to restrict the values to a list (hence the List
table). You can also set the object to query for a list, using any abstract SQL needed.
Finally, yes the values are serialized back to the Values table....with an instance ID and a def ID...
Feb 24, 2006 02:55 PM|codegalaxy|LINK
That sounds so close to how I was thinking sort of about it
Can you expand on it just a little -
if everything is serialized into one field in the values table how can I report and pull back into a form to edit it
and how can I design the form? I was thinking again of some sort of parser where I put in some sort of code that would then be able to place form elements in a layout from these tables you mention - does that sound like an idea?
Unfortunatly this will be a requirement
Feb 24, 2006 03:27 PM|RLyda|LINK
Feb 26, 2006 02:16 PM|rodneyjoyce|LINK
Feb 28, 2006 04:40 PM|codegalaxy|LINK
could you post or send me a file showing the layout of the tables - not sure of all the info I need for a field or a list etc. - want to make sure I get it all - the timeframe for this just got moved up a lot