Hi,

 

I am looking to have an arrangement where can create a new record in a table, but once they've left that record they can not edit it again - view it yes, but not change it.

 

I've looked at the custom privilege set and on a field and a record level can have none, view or full. There also seems to be an option where security can be applied by a calculation. Would I be looking to, say, compare "now" time with the record created time and if they differ by (>x) then...?

 

Any suggestions would be appreciated.

 

Thanks,

Greg

In 'Custom Record Privileges' you can select Edit [no], Create [yes].  IIRC, this allows editing of a newly-created record until the end of the current session.

 

Another option is to auto-enter a serial number on record commit. Then allow record editing only when IsEmpty ( SerialNumber ).

Good point Comment. Can you clarify what "current session" means?

Until they close the file?

Until they navigate to a layout based on another table?

According to my brief test, they can still edit the record after leaving it but next login they can't edit it any longer, as you describe.

Thank you Comment.  

 

Both options sound good. What is IIRC please?

In Custom Record Privileges, I suppose Field Access is All, and View is Yes?

 

As per BruceR's question, does "session" mean logout?

 

Cheers,

Greg

IIRC = If I Remember Correctly

 

session = until you close the file (or logout ) - i.e. the same scope as $$variables (or globals in a hosted file) have.

Set Edit Records privilege to Limited, and enter a 0 as the value.  As soon as the record has been committed, it is locked. Users will inevitably lock themselves out of a record prematurely by any of the various ways to commit a record.  Some of that behavior can be attenuated by strict UI controls.

 

Steven