I think the problem here will be in the database design. You certainly could store PDFs or the like, but then someone is going to want to run queries, produce reports, make updates etc etc.
The problem (I think) is to come up with a db design that is not fixed to a given form structure. Using the relational model this is going to be tricky. I'm sure someone somewhere has done something along these lines but to what level of success I've no idea. I have (in the past) been involved with non-relational data models that could possibly overcome the db design issue, but you are then looking at having to use technologies that are maybe new to you and possibly costly. For example using Java/XSLT with a non-open source database server. However, having said all that the PHP-General mailing list is probably not the place to be discussing this. Graham > -----Original Message----- > From: Shaun [mailto:[EMAIL PROTECTED] > Sent: 14 October 2004 18:23 > To: [EMAIL PROTECTED] > Subject: Re: [PHP] User Defined Forms > > > > "Jay Blanchard" <[EMAIL PROTECTED]> wrote in message > news:[EMAIL PROTECTED] > [snip] > I am creating a site where users record details of their clients and > record > their progress. The whole point of the system is to reduce the amount of > paper work and store everything online. > [/snip] > > > How much time have you spent with the users? How well do you understand > their needs? Have you done a flowchart or any other modeling? > > Hi Jay, > > I have interviewed a few users and it has become instantly apparent that > they all work differently and record slightly different information about > their clients making it impossible to produce a general set of forms that > would encompass all users. I haven't done any other forms of modelling as > yet. > > Thanks for your help > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > > -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
