Couldn't you just change the capabilities of the groups where these files
reside?  After all the HP3k systems will only be used for look up.  By deleting
the write capability from the account(s) this should prevent anyone from writing
to any file in a given account.

I will waite and then ponder your responses.

Larry Barnes

John Krussel wrote:

> This can be a though one since some applications do a write to the database
> just by starting them up.  My best suggestion would be to do something like
> what you suggested, except don't delete the write classes, just change all
> write and read/write classes to read. That way if a application opens it
> read/write (even if it's just going to read, and there are a ton that do) it
> will most likely still function. And for those that do try to update it will
> fail.
>
> John Krussel
> Systems Manager
> Nordstrom.com
> [log in to unmask]
> http://www.nordstrom.com
>
> > -----Original Message-----
> > From: Rudderow, Evan [SMTP:[log in to unmask]]
> > Sent: Thursday, September 09, 1999 10:40 AM
> > To:   [log in to unmask]
> > Subject:      Converting applications to read-only
> >
> > Hi all,
> >
> > We're converting from our HP3000 "legacy" applications to an ERP real
> > soon now; management has decreed that the HP3K apps must still be
> > available for lookups but that nobody should be able to enter new, or
> > modify existing, data.  I figure the simplest thing to do is change all
> > of the databases so that the write class list is empty.
> >
> > Anyone else got any ideas?
> >
> > Thanks
> >
> > Evan