I have a solution that will require 150+ forms with multiple pages and requires the storage of between 10 and 130 fields of data per form. The data types will be all varieties blobs, varchar, text, int, numeric etc etc
What I have done in the past with Lasso and ColdFusion is use two table normalized approach ie
Form Table
Form_Content Table
Where content is stored with a reference to the form and a sort order.
I am in a quandary how best to approach this with Servoy:
a) Do I carry on with a series of globals and then post them to the database using the normalized approach
OR
b) create multiple tables one for each form in my database
Key considerations:
I have normalized data to insert at some point in the future
This is sold as an saas solution and hence has several clients some of whom have many 000’s of form records
I want to be able to export data to excel easily and having one table per form lends it self it this approach
This is not a massive hit site so speed is not really an issue 2-3000 form submissions a day would be quite high.
Take a look at the data structure used by the sample pdf form solution. It is elegant in its simplicity. It does require that you store your data as text field name/field value pairs (which is also good for xml). We use it for 650+ forms, some of which have over 500 fields per form, to store many millions of records, with no problems.
Based on your requirements, this will probably not take care of all your needs, however it is worth considering.
Take a look at the data structure used by the sample pdf form solution. It is elegant in its simplicity. It does require that you store your data as text field name/field value pairs (which is also good for xml). We use it for 650+ forms, some of which have over 500 fields per form, to store many millions of records, with no problems.
Based on your requirements, this will probably not take care of all your needs, however it is worth considering.
May be I don’t understand you correctly, but we are designing the database at least in 3rd normal form and design the application independant of how the database is designed. Was never a problem, even with large amount of data.
Or did I completely misunderstand you (I am not sure as I don’t understand Westys answer as well)
May be this helps, Robert
Gordon:
Hi
I have a solution that will require 150+ forms with multiple pages and requires the storage of between 10 and 130 fields of data per form. The data types will be all varieties blobs, varchar, text, int, numeric etc etc
What I have done in the past with Lasso and ColdFusion is use two table normalized approach ie
Form Table
Form_Content Table
Where content is stored with a reference to the form and a sort order.
I am in a quandary how best to approach this with Servoy:
a) Do I carry on with a series of globals and then post them to the database using the normalized approach
OR
b) create multiple tables one for each form in my database
Key considerations:
I have normalized data to insert at some point in the future
This is sold as an saas solution and hence has several clients some of whom have many 000’s of form records
I want to be able to export data to excel easily and having one table per form lends it self it this approach
This is not a massive hit site so speed is not really an issue 2-3000 form submissions a day would be quite high.