RE: Normalization was Left AS/400 and Returned

I completely agree that users should not be allowed to update production
data except through the application programs.  The one exception I can think
of would be interfaces that use data uploaded from spreadsheets and whatnot.
That data, of course, should be processed by an application program that
logs the event, edits the data, and produces a report.  We have a couple of
those here for Lawson.

I keep reading about the benefits of stored procedures on this list and
intend to explore their possibilities at some point.  For the present, I and
my colleagues have more pressing issues.  That's what happens when a
development staff is half the size it needs to be.  The good news is that if
we need to make a database change, we do and notify the "power" users of
that change so they can make appropriate modifications to their queries. 

Donald R. Fisher, III
Project Manager
Roomstore Furniture Company
(804) 784-7600 extension 2124
DFisher@xxxxxxxxxxxxx


<clip>
Not an issue for me.  I don't give users direct access to production data
using PC tools.  First, I never let users update production data using PC
tools; that to me is absolute insanity (and I doubt it would
pass any Sarbanes-Oxley audits, either).  Second, if they really need the
data, I'll write a stored procedure.

Why do this?  Well, if I have to change the database layout, I can.  If I
have users directly accessing tables, then every database change affects all
of their spreadsheets, and now IT is held hostage by MS Access.  That's
simply not acceptable.
<clip>