prevent deletion working erratically
Jean-Pierre A. Radley
appl at jpr.com
Mon Dec 16 13:13:25 PST 2013
Jeff Harrison propounded (on Mon, Dec 16, 2013 at 12:56:25PM -0800):
| > From: Jean-Pierre A. Radley <appl at jpr.com>
| >
| > |
| > | In a database I have set [Y]es to prevent record deletion from screens that
| > are not password-protected; it works as expected.
| > |
| > | In another database, I can nonetheless delete records from such screens.
| > |
| > | What am I overlooking?
| > |
| > | --
| > | JP
| > _______________________________________________
|
|
| I'm sure I'm understanding what you are saying.
|
| What do you mean by "In a database..." do you mean within 1 filepro "file"?
I do not call it a file when it is a database consisting of a directory
comprising many files, including key, prc.input, screen.1, index.A, etc.
:-)
| Say you have a file called "customer" and within this a screen called
| "A" where you have saved [Y]es for record deletion.
|
| Are you saying that you have another file called "customer2" and a
| screen called "A" and record deletion is not working there?
|
| You of course need to make sure that you have [Y]es for record
| deletion saved in the 2nd file/screen as well.
Quite the contrary. The [Y] option is set in order to PREVENT record
deletion from a screen, while [N] DOES NOT PREVENT record deletions.
In "customer", Y does prevent deletion from screens so tagged, whereas
in "customer2". deletion is allowed regardless of whether the screen is
tagged with Y or with N.
--
JP
More information about the Filepro-list
mailing list