RE: Athuorization lists

["Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>]

> From: Fisher, Don
> 
> 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.

This is fine.  They're not uploading to your master files, they're uploading
to files specifically designed to be imported.  One then hopes that the
import programs do a really good job of checking for valid data :).


> 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.

One option is to pass in an environment ID and let the program change its
library list dynamically based on the environment.


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

And I guess if it's read-only access for power users, you can probably
justify it.  But like I said, change a single table or column name, or
change the format of a field, or any of a number of other things, your power
users are going to have to change their queries.  As long as they accept
that, it's fine, but in many organizations that becomes a reason to ban all
database changes.

Joe