RE: Athuorization lists

["Fisher, Don" <dfisher@xxxxxxxxxxxxx>]

Allowing data uploads from spreadsheets and the like was a requirement for
us since our Lawson package allows data to be imported for invoice and
general ledger transaction creation.  We created a specific group profile
for this function and granted the profile data change access to the specific
files used for these functions.

We wound up creating a group profile that has read access to our files so
our "power users" could run queries via MS Access and download data to
various spreadsheets.  Stored procedures would probably have been a better
way to handle that, but we run multiple production environments on a single
system and I haven't yet figured out how to make a stored procedure respect
a library list.  The definition of the procedure requires a library
qualifier on the external call to an HLL program.  

We didn't have the time to write those things anyway, so the point is moot. 

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

<clip>
1. Don't allow external updates to your files, except for specific batch
input files designed for the task.  (In the ante-diluvean days these had
names like "batch input" or "suspense" files -- or EDI files).

2. Understand that having users directly access data means that changes to
your database wreak havoc throughout your organization.  Not only that, but
they need to understand the intricacies of how your data is stored.

Allowing access through shadow files, stored procedures and message-based
servers allows you to make database changes without affecting your users,
including the ability to have combinations of online, offline and nearline
storage without their knowledge.  But there is a cost: you have to keep the
interfaces up to date, and some people don't have the time to do that.
<clip>