Restrict field access by calc?

[hayesk]

I want to enable a user to be able to see all of the fields for records they own (indicated by a "Record Owner" field, but for other users' records, I only want the user to see a few of the fields.

Is there a way to do this?

[Vaughan]

It may be easiest done by controlling the record navigation in your interface (disable menus and status area and provide scripted buttons) and switch layouts.

[Hijack]

Man, I really like to have a solution for this too. In my particular situation, I have a portal showing notes from database users (notes in reference to a top-level IT support request). I only want notes to be visible to the person who enters them. I can do this on a full table validation of "Get(AccountName) = Created By" in the View portion of the table security but that leaves a bunch of records in the portal with <No Access> in the visible fields for those who can't see the secured entries.

That then leads to a mis-sorting of the portal (normally based on creation date then time) since that info isn't readable to the client copy of FM.

[Vaughan]

How about display a calc field instead of the notes, which returns null if the access isn't kosher?

This will screw up data entry a bit though...

[hayesk]

Thanks, Vaughan.

I'm going to use a combination of calc fields and layout access. I am worried a bit about exporting records though. I want the user to be able to export their own records, but not the records of others - this could be tough.

[Fenton]

I was recently having a problem with Copy All Records, which needs Export Privileges. But I didn't want to turn it on for everyone (basically gutting the security). What I did was just turn on "Run with full access" for that particular script/routine. It worked fine.

So, if they could only export with your script, you could include a Go To Related Record [show, AccountName relationship] in the script.

[Hijack]

How about display a calc field instead of the notes, which returns null if the access isn't kosher?

This will screw up data entry a bit though...

Yeah, I was thinking about that direction but knew the data entry issue would be a little tough to get around. Ah well, I'll let my subconscious mull it around for another couple of weeks and I'll wake up one morning with a good solution on my mind.

Thanks for the advice.