--- Petre Agenbag <[EMAIL PROTECTED]> wrote: > This is exactly what I'm looking to do; but my problem > remains: I don't know what the best solution is. The > problem is clear: the users actually need an electronic > copy of the data they submit; they must revisit certain > issues annually, and would need to access the data they > submitted the previous year; either for review purposes, > or to make the new submission a speedy matter of simply > changing the details that are different from last year.
In this case, it sounds like you need to just keep this data on the server in your database like you are already doing, then you simply provide another Web application that uses the same database and allows them to search, modify (?), and display the data for printing. You can generate reports, graphs, and all sorts of things that they will appreciate. Don't restrict yourself to their line of thinking. :-) > It's much like a normal office scenario: each person > works on Word docs that need to be shared with others, > yet needs to be editable and must be saved etc, BUT the > difference here is that the data of all the collective > sources must be entered into a central db. So the "non > technical" solution would be for the users to do the > forms in "word", then fax it to the central office, > where you have a temp type the data into the db... we > can't have that now... The solution is for the users to "do the forms" in a Web application that you build, and your Web application stores the data in the database. Forget about data entry personnel. Chris -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
