I have a very strange problem with an in-house custom database.
One of the forms has three computed subform formulas.
Most documents using this form can be opened with no problems, but a couple of documents (using the same form) produce the error message:
“Error, the form and subform Reminder Details Edit both have a field entitled ActionReminder”.
The error message appears to be a lie.
The field “ActionReminder” only exists on the subform “Reminder Details Edit”. There is no such field on the form.
I’ve also checked the computed subform formulas and, for the documents producing the error, they should evaluate to the same subforms as they do for most of the error-free documents.
I’ve tried opening the documents in three Notes client versions: 8.0.0, 7.0.2, and 5.0.13. The bahaviour is identical for all of them.
Can anyone explain how, out of hundreds of documents using the same form, only a couple produce this error while all the others work fine?
Subject: Form and subform both have a field entitled ActionReminder
Could it be that there is on your document already a field called ActionReminder? You can check this by looking at the fields (2nd tab of the properties window)?
Subject: RE: Form and subform both have a field entitled ActionReminder
Yes, the “broken” documents have that field, but so do most of the documents that work.
Anyway, that’s the normal situation: create a new document based on any form that uses subforms (computed or not), and fields on the subforms are saved with the document.
Subject: RE: Form and subform both have a field entitled ActionReminder
Could it be that the broken documents have data that results in a different calculation for the computed subforms? And could that result in 2 subforms that each have the duplicate field?
Subject: RE: Form and subform both have a field entitled ActionReminder
“Broken documents producing a different calculation for the computed subforms” is certainly something I’ve considered.At a colleague’s suggestion, I tried an experiment to that effect: I commented out the normal formula for the subforms, and used text constants for the computed subforms instead. This should result in every document using the same subforms regardless of any field values, but the error is still the same: two documents broken while all others work fine.
Another interesting thing, though I don’t know whether it’s relevant: the two broken docs were created by one specific user. No other user has managed to create docs that produce the error.
Thanks for the responses, Rob. Your effort is appreciated, even if we can’t find a solution.
Subject: Form and subform both have a field entitled ActionReminder
We do have the same problem in one application. The name of the field is our case the first field in the subform.
The intermediate solution we have is to create one agent that replace the form to another without the subform. Open it in UI and save it. After that, replace the form back to original form.
The reason for this is still unsolved, but it started to happen when the server was upgraded from 6.5x to 7.0x.
Maybe this can be some help for you. I am also interested to hear if you have found the reason for your problem.