What's the best way...

[Chris Sharman]

>I'm a little bit puzzled by your statement that quick has to open the
>file/table in read/write mode.  Security can be implemented on many levels,

We settle for the quick & dirty solution of putting the user in find mode &
erroring in preupdate here: a long way short of ideal I know.

All the clever mods Bob suggested to prevent the user entering or changing data
will work, but the Quick screen will insist on opening the file for write
access, and if it can't the screen will fail at startup: the user won't even be
able to read anything.

You have to go to separate .qkc files to get the files opened readonly, and I'm
not sure offhand how much code you have to write:

Ideally "screen ... activities find ..." would be all, but I suspect you may
need "file ... open read ..." on the appropriate files, display on the fields,
maybe disable on the update procedure.

I suspect many/most screens could usefully be run in two modes: readonly &
read-write. Powerhouse gives no nice short cut to doing this, leaving us to
write extra code, and mess around with 2 or 3 screens where one could do.
______________________________________________________________________
Chris Sharman			Chris.Sharman@CCAgroup.co.uk
CCA Stationery Ltd, Eastway, Fulwood, Preston, Lancashire, PR2 9WS.
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau.edu
Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
powerh-l@lists.swau.edu is gatewayed one-way to bit.listserv.powerh-l
This list is closed, thus to post to the list, you must be a subscriber.