I have Text/Editable field with a DBlookup as the translation value. The lookup works fine on the document.
When I save and close the document, the name and address window appears asking me to select the user to send to. It is trying to send a message to the value in the Dblookup field. It is not a username/group, so it brings up the ambigious name window.
If I remove the @DBlookup formula, the document saves and closes just fine; but I need the @DBLookup value in that field.
I am having no success in stopping the document from sending. Is there something I need to set in the field properties?
@DbLookup does not cause sending email. As Yazdi Bulsara indicated, this is caused by properties of the form and field.
What’s the name and type of this field?
Do you observe the difference when you remove just the @DbLookup formula, or when you remove the field entirely? What about if you do not remove the field, but you do type a value in the field?
Is the “Send on save” option of the form enabled?
Do you have a Mailoptions field and if so give details about this field.
The field is named “TeamDisplay” and it is a text field set to be editable.
I see the difference when I remove the @dblookup formula, and leave the field on the form.
I added a value to the field and got the same result.
The send and save options on the form are not enabled.
There is a “mailoptions” field (should of caught that earlier). The default value is “0”. I cannot find anyplace where the value is being set to one.
I set the “mailoptions” field to not be hidden, opened the form with the dblookup in place. The field still says at “0”. The mail send dialog still comes up.
Delete the MailOptions field.Since you get the same problem without the @DbLookup, I think you have definitely ruled out the @DbLookup as the source of your problem.
TeamDisplay is not a special name to Notes, and if it’s a regular text field, I can’t think of any reason the system should expect it to contain email addresses. Is there some other field, whose formula refers to the TeamDisplay field? A field called SendTo, CopyTo or BlindCopyTo, perhaps?
Is there any event code – Querysave or Postsave or onsubmit – that might be causing this dialog to appear?
Actually, the problem goes away when I remove the @Dblookup formula.
I tried deleting the mailoptions field, but still get the mailsend dialog.
I checked the QuerySave,PostSave and OnSubmit options on all of the fields of the form: Found this script on the “Exiting” option on my field and several others:
Sub Exiting(Source As Field)
Dim workspace As New NotesUIWorkspace
Dim uidoc As NotesUIDocument
Set uidoc = workspace.CurrentDocument
Call uidoc.Refresh
End Sub
I do not know LotusScript, but can figure that it must be refreshing the document or fields.
When the document is in edit mode, I can click on the fields (text/editable and comboboxes) with this option set and the mailsend dialog will pop-up.
I have removed them and it is no longer prompting the mailsend dialog when I click the fields, but still wants to send when I save and close the form.
I will continue to search for this code in more places.
Now, Where the code came from you ask? Wish I knew, I created this form/database from scratch and have never seen it on any of my other fields/forms.
The only reason that I’m not insisting that you supply the exact @DbLookup formula and tell where it is, is that I’m very very very certain that the @DbLookup function has nothing to do with your problem. There’s no relationship between @DbLookup and mail sending. It only has to do with what data are in the field.
I must have misunderstood you. You said:
I see the difference when I remove the @dblookup formula, and leave the field on the form.
I added a value to the field and got the same result.
I understand this to mean, you took out the @DbLookup formula but left the field on the form, and did not get a mail dialog. But if you type some text in the field, you do get the mail dialog. Is that correct? Incidentally, when you try this, it probably makes a difference what text you enter – you would only see the dialog if the text you enter is an ambiguous mail address. Try what happens if you remove the @DbLookup, but enter the same text that the @DbLookup would put in the field. Or leave the @DbLookup in place, but delete the value that it puts into the field.
Use the menu File / Database / Design Synopsis to get a complete description of the design of the form. Make the synopsis include just the one form, and every subform that’s on the form, and all shared fields. Then you can page through all of it and look for anything suspicious. Especially, search for “mail” – perhaps there’s a formula that uses @MailSend. Also look for any shared fields
You clearly didn’t construct this form from scratch in the sense of manually creating each field and formula. I believe that you didn’t copy the entire form, but the only way you can get event code in a field without writing it yourself, is by copying an existing field from some other form.
in support of Andre - I too can confirm, @DbLookup is nothing to do with sending mail, it is something else on the form performing the send, are you sure you’re not referencing the with field with an @MailSend somewhere on the form?
You are correct, I did copy some of my fields from another form. This may of caused the problem. (trying to save time - ended up wasting yours - Sorry)I will be more careful when borrowing code/fields etc.
I couldn’t ever find any @Mailsend code, but highly suspect that it was there somewhere.
I ended up re-creating all of the fields on the form from scratch. The problem went away. Of course, now I don’t know what caused it, but it is working.
Sorry for the late response, had a couple of days off.
I had the same problem.You’re probably working on this form for a Workflow, at least it’s what I’m doing. Problem comes from the (OS Domino Workflow Information) subform which contains an event called “PostModeChange” and which tries to refresh everytime you switch to edit mode. Removing the refresh prevents the problem, I don’t know if it has any side-effects.