revb2b,rdesign,pre-prompt subroutine (AREV Specific)
At 24 MAR 1999 07:03:27PM Richard Wilson wrote:
Ok brush of the dust. Does anyone remember if Rdesign allowed
pre-prompt subr's. I tried playing with paramenter 1 but that does
not seem to be part of pre-prompt logic.
I have a need to password an existing field before any modifications
can be made
TIA, Rich
At 25 MAR 1999 06:48PM Capt'n Kirk wrote:
R/design does not allow for a pre-prompt process but does allow for a pos-prompt process from which you can validate the password and discard or save changes as appropriate.
Is this 'prompt for a password' required on the record key or a data field? Is it prompted for each record or just upon entry to the screen?
Capt'n Kirk
At 25 MAR 1999 06:56PM Victor Engel wrote:
If memory serves me, there are facilities for both null default and input conversion. You could put login in a symbolic null default field or a UDC (user-defined conversion).
At 25 MAR 1999 08:45PM Richard Wilson wrote:
I am getting responses, great. however there seems to be some
confusion as to what I desire.
There is a data field call TEAM (field 7)
1)New record or existing record and TEAM=null
allow anyone to change TEAM without password prompt2)Modify mode on existing record and TEAM has a value
prompt for password and if correct allow mods to TEAMif incorrect take user back to mods line
At 26 MAR 1999 02:14AM Victor Engel wrote:
This is pretty much what I understood you to mean. I see in reviewing my answer that I have a typo: the word "login" should read "logic". I can see how, especially since we are discussing passwords, that you may have thought I was referring to a login process. I was not. Sorry for the confusion.
At 26 MAR 1999 07:33AM Richard Wilson wrote:
Thanks for all the suggestions. I went with the post-prompt logic
I would have preferred Pre-prompt, but it is now working so I'll
live with what's available
Thanks