Fields - prohibit Entering?

Hi, I would like to block people from clicking in certain fields (in edit mode). Perhaps display a popup box saying they cannot modify the field. I wish the “Entering” sub was similar to, for example, “QuerySave”, in that it would be useful to have ‘Continue As Variant’ as an argument to stop users from entering.

As is…I’m currently hiding fields left and right and it’s getting quite messy and very annoying because I don’t want to hide the fields and data…only keep certain users from changing them…

I also heard notes 8 allows enabling/disabling of fields, unfortunately we don’t have Notes 8 yet even if that is true.

Does anyone have any solutions they would share with me? Would appreciate it much. Thanks.

Subject: Fields - prohibit Entering ?

I would suggest using Controlled Access sections. The drawback may be that you’ll need to group these “protected” fields together into a common section. The advantage is that you can control who can edit fields inside these sections.

Subject: Fields - prohibit Entering ?

Um, Notes 7 allows disabling of fields. That’s what the “Input Enabled” formula slot is for.

Subject: Fields - prohibit Entering ?

When you stated that you want to “stop users from entering…”, do you mean all users or certain ones? If you meant all users, just create a computed for display field. If you want to restrict certain users from editing the field, you may need to put users in a group, include that group in the ACL and assign a role (or two). Then your form could use a hide-when formula (show the editable field for some and the computed for display field for others) based on the role.

Hope this helps.

Subject: Wish i could…

I’m afraid i cannot modify anything related to the ACL. I have a form, where 3 different people will need to change (at a total of 4 different stages of the form). These 3 different people are acquired in the 1st stage of the form and stored as 3 different fields. The form fields which are hidden/shown are reacting to whoever has the form open.

Involving the ACL would be on a much higher level of scope and i’m in a much more specific scope.

I suppose i could have 2 fields for each form field…one for editing purposes, and the other for display purposes…and set them up for only one of the fields to be shown at a time (depending on the user and stage). Though, this is very sloppy to me and makes me want to run screaming back to C#/C++…i’ve looked over some of the pre-existing forms here…huge and extremely sloppy in this type of manner…

Subject: RE: Wish i could…

Graham is correct with the section control. If you group the fields, you can limit who edits by role, user, or fields. You can also do more then one grouping if needed.

If you have a few fields then use the Field object “Input Enabled”. I just upgraded to 8, but I was using this feature in 7.0.3, check to see if it is in your version.

Hope this helps,

Teri

Subject: question…

I have 7.0.3 HF77. I looked in the Help Topics and it did have a page to let me know that “input enabled” was used for Native OS style fields. Mine are these, but i don’t see where i could enter in the formula for calculating a @True or @False for enabled/disabled. If there is supposed to be a forumla box in the field’s properties next to the Native OS selection, i’m afraid i don’t have it. That, or I am just not understanding how to use “input enabled” exactly?

Subject: RE: question…

When you open the form within your designer. Click on the field that you want to restrict. Set it to editable.I checked one of the fields and regardless if you choose the Notes Style or the Native OS style the Input Enabled object is within in the drop down list on the Objects tab. The code is wrote within the (FIeld): Input Enabled formula screen. This is the same place you would place the code if you have the field set to any of the computed styles.

Hope this is what you want.

Subject: must be the version

I’m afraid i don’t see that. I assume it is my version of Notes than. Fortunately today i just received an email saying we’re finally switching to Notes 8…next week. This option would help a lot. Thanks:)

Subject: Fields - prohibit Entering ?

This can help you.YOu just need the code to select who will have access or not.

Sub Entering(Source As Field)

Dim uiws As New NotesUIWorkspace

Dim uidoc As NotesUIDocument

Set uidoc = uiws.CurrentDocument

<code to check access>

if <restricted> then

Print "You are not allowed to amend this field"	

Call uidoc.GotoField("Other Field")

End If

End Sub

Subject: Indeed yes

I will try the redirectional method. I hope that will work as there actually isn’t a common editable field i could redirect the different users to…meaning each have their own… In which case i think i’d have to make different IF cases for each type of user and direct each type to a field which is editable to them. I’ll see how she goes

Thanks