Comments on: Data Management Malpractice https://effectivedatabase.com/data-management-malpractice/ Making data management a revenue generator Tue, 28 Apr 2020 19:43:26 +0000 hourly 1 By: Wes Trochlil https://effectivedatabase.com/data-management-malpractice/#comment-911 Tue, 16 Oct 2007 20:13:02 +0000 http://effectivedatabase.com/2007/10/15/data-management-malpractice/#comment-911 Thanks for clarifying that, Terry.

]]> By: Terry Dowdy https://effectivedatabase.com/data-management-malpractice/#comment-910 Tue, 16 Oct 2007 20:10:09 +0000 http://effectivedatabase.com/2007/10/15/data-management-malpractice/#comment-910 Thanks for posting this Wes (your edits definitly improve my writing and spelling issues). In regards to my comment about where the AMS firt into this picture, I was thinking about one of the comments posted on the original WaPo article asking if any contributor data was exposed. Also, since many AMS’s tie to an organizations accounting package, such as Great plains or Solomon, some organizations actually put their vendors in the AMS, and when paying out reimbursements they consider their staff as vendors, and therefore they end up in the AMS.

Additionally, if one type of data (employee records) is exposed, who is to say that other types aren’t also in jepordy. Customers and users will quickly forget all of the good things that happen, assuming they evemnm know about them, but the bad stuff stays alive in memories for a very long time.

]]>