I too use the same ::MN method in my DP apps to lock a record. Works
very well.
For instance, I have an app that tracks incoming payments and compiles
them into bank deposits. Once a payment is assigned to a deposit, I
don't want it being altered. The ::MN field normally says "Un" (followed
by a ::C field that says "deposited") when the user can edit the entry.
Once it's assigned to a deposit, the ::MN field changes to blank and the
::C field changes to "Deposited". With the ::MN field blank the record
is locked. I also add some help text to that ::MN field telling the user
why they can't edit and save the record and what they have to do if they
absolutely must edit the record. The nice thing is that since you don't
normally TAB to a ::MN field, the user doesn't see the help text unless
they try to edit the record and get blocked.
Tim Rude
On 2/9/2015 6:03 PM, Ed Marfil, MAST UNITED wrote:
Hallo Jaap! Hoe gaat het?
Why does it seem that the largest and longest continuous DP user group still
around is the Dutch. Thank goodness for the Dutch practicality to keep on with
what works.
Your method is definitely worth checking out. I'll work on it soon and let you
know how it goes.
Dankjewel en vriendelijke groeten,
Ed.
P.S.: I've pretty much exhausted my Dutch vocabulary at this point :-)
-----Original Message-----
From: [email protected] [mailto:[email protected]]
Sent: Monday, February 09, 2015 3:11 PM
To: 'Dataperfect Users Discussion Group'; MAST UNITEDEd Marfil
Subject: Re: [Dataperf] Change record attribute.
Hi Ed,
I've been doing this for many years, by adding a single U2 field to every financial panel with a
<::NM> extension. Thus the user cannot alter the record if the field is blank. Next make a formula,
stating one (or as many other criteria) as necessary under which the panel may not be changed. If the
panel would be changed, the formula should display nothing, and the record eventually can not be saved.
In case the record is allowed to be changed, the formula should give an "OK" (or "Y",
saving some space in the indexes) reading, so the record can be altered.
However, this method alone does not prevent values to be entered through links and doors! In that case, I double the fields that carry
the financial data, and create a loop between each pair, thus mirroring the data; "YES or "NO" depending on the setting
of the switch. So the field will only accept "outside" data if the switch is open. When "closed", set ""
(blank) or "N", the field should respond to an outside change by copying it's previous mirror value.
These loops work surprisingly well in DataPerfect and I have successfully
applied them to many interlinked panels holding part of the input.
Hope this will get you going,
Jaap.
--------------------------------------------
On Mon, 2/9/15, Ed Marfil, MAST UNITED <[email protected]> wrote:
Subject: [Dataperf] Change record attribute.
To: "'Dataperfect Users Discussion Group'" <[email protected]>
Date: Monday, February 9, 2015, 7:48 PM
Good day to all. I’m hoping someone has a way and would please share it, how to make a record no longer changeable (or make read only) after a related record is marked closed, i.e. a record in a panel where user enters costs can no longer be updated or revised once a bill or invoice has been issued final. I remember something related to this attribute briefly discussed in the last DP Conference (ages ago) but it was with the use of DP Mouse and Shell. I use neither so am hoping there is another method to achieve the same or similar result. Thanks for any suggestion.
Ed
Marfil
-----Inline Attachment Follows-----
_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/cgi-bin/mailman/listinfo/dataperf
_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/cgi-bin/mailman/listinfo/dataperf
_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/cgi-bin/mailman/listinfo/dataperf
