Hopefully I’m overlooking something and don’t have the problem of a corrupt design, but so far I have no clue.This is the problem:
In my application I have both in a view and in a document an action button with action:
@Command([Compose]; “SUsers”)
There’s are a couple of forms in the database of which SUsers is one. However, Notes simply refuses the compose a document with this form and takes another form to create the document with. It does this from all documents and views, except one view. There the same action works fine.
Does anyone know of anything that might cause Notes to pick another form to create from then the given form in the formula mentioned above?
And the Notes help nicely mentioned how to prevent this problem:@If(@IsNewDoc; @Return(Form); “”)
as start of the form formula
How can I change it to enable me to create forms based on this other form (which is actually a response doc to the documents based on the NewPres/Present form)?
Subject: @Command([Compose] giving very weird behavior
Yes, look at the notes help for “Form formula” - I think this may be what’s causing your problem.
If not - is SUsers available to the client you’re trying to create it in? If not, notes will probably be defaulting to the default database form to compose the document.