Why should anything about those records be editable?
Sounds like a structure problem.
Can you describe these tables please?
no structure problem, the administrator wishes to allow users to edit/update non-critical informations in any records in fields which are basically notes fields.
The the other hand "Date" and "Price_Paid" are critical information that should not be edited by the user after the record is at least one day old.
Put these fields in a separate related table.
1 of 1 people found this helpful
If your only concern is the user changing the system date use GetAsDate ( Get(CurrentHostTimestamp) ) instead of Get(CurrentDate). This will return the date of the server.
This won't work if you solution is not hosted of course, but your case suggests it is.
The solution is going to be used also without FMserver, but interesting hint I didn't know that, Thank you
this is part of the inherited solution that I posted on Portal and Duplicates
Trying to make it simpler and I wish to avoid creating even more Tables of the already >80 that I have (the relationship graph looks terrible already).
Our strategy is running a script at 1 AM, quickfinding records having 0 in a specific field (it's the autoenter value) and doing a replace field contents with 1, which is the value locking the records for specific privilege sets.
If you don't use a FM Server setup you can use Task Till Dawn to open a FM DB that calls the script in your main DB.
Nevertheless, it is a fairly simple way to do what you need.