A field is a Notesitem object in the LotusScript classes. NotesItem does not have a ReadOnly property, nor does it have a Visible property.
Notesitem does have an IsReaders flag, meaning it is a Reader field and thus controlling access to the document the field is in.
As for visibility, on the document that is controlled by Hide/When formulas and concern layout, not field information. Thus, there is no way to control that by code outside of the Hide/When formula.
Could you be a bit more specific as to what you need and intend to do ?
I've a LN database that includes a form. The endusers are requesting the option to create templates, but there's no such possibility in this database.
What I'm trying to do now is create this possibility in Excel where I programmatically recreate this form (I'm accessing the form from a VBA module in Excel), but some fields are hidden and others get automatically filled in and are restricted from change by the user. I'd like to test the fields for these properties and set the fields in my msform accordingly.
I can hardcode these properties as I know the fields that have these settings, but I'd prefer to have the code determine the settings from the original form in Lotus Notes.
Testing on that IsReaders property would probably help me out and I may be able to get the Hide/When formulae to determine if my fields need to be hidden. Could you point me to where I might find these formulae?
Do you have the Notes Designer installed, with Designer-level access to the database ?
What do users mean by creating "templates" ? I suppose that means that users want the form to contain pre-filled text that they choose whn they create a new document based on the form.
It's not too difficult to implement. You need another form with fields containing the prefill values, the you need some code to ask the user which "template" he wants, get the corresponding document and create the new document with the prefill values.
Do you have someone who could do that ?
yes, I know that within LN it's not that difficult, but I don't have Designer-level access and the people that do tell me that it can't be done due to licensing constraints.
The solution I'm going for is to have a button where people can select an existing document and it'll just populate the new document with the same values. Apparently this does not conflict with the licensing.
I think it'll still be interesting to know where these Hide/When formulae are residing as I won't be surprised if management decides that the above solution isn't good enough after a while.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.