> >> For lack of experience, I don't know if such update (update 16 entries > >> by client) is normally acceptable or not? > ... > > the same way all 16 times? The real solution to that, IMHO, is to adjust > > your HR policies to make is easier to fire people. > Haha. Awesome.
I was being completely serious. :) Data has value, and entering crap data creates costs down the pipe and reduces efficiency. You'd consider firing an employee who scribbled all over the walls because it would be an inconvenience and incur cost to clean it up, and it demonstrates something about the employees respect for the organization. Data entry isn't any different; and all the design and technology can't defeat laziness and/or incompetence, data models shouldn't be tortured to try any work around such things. If there is a solution, or partial solution, to such problems it ultimately is the client interface. Data models should fight for data integrity and completeness, not try to fight against the stupidity of the user. -- Adam Tauno Williams, Network & Systems Administrator Consultant - http://www.whitemiceconsulting.com Developer - http://www.opengroupware.org --- You are currently subscribed to [EMAIL PROTECTED] as: [EMAIL PROTECTED] To unsubscribe send email to [EMAIL PROTECTED] with the word UNSUBSCRIBE as the SUBJECT of the message.
