[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 257
  • Last Modified:

Use second form not dialog box

How do I have data stored using one form, but for a small number of fields, I want to have data entry & validation done on a seperate form. I cannot use the dialog box.

All code & suggestions greatly appreciated
0
paulhollamby
Asked:
paulhollamby
1 Solution
 
GwrCommented:
Hi

Try having a generic address .. one that would be create automaticly by your App or by an Action. Modify it and save it as in a new name ... Create doc .. Copy all items .. ReplaceItemValues and save

Gwr
0
 
paulhollambyAuthor Commented:
I need to have multiple addresses. For some contacts their may only be 1 address, but for others their will be 3,4 or more addresses.

These addresses will be summarised on the contact form ie To edit, the data will be edited on the address form, and when saved, be updated on the contact form.
0
 
marilyngCommented:
Paul,
Just browsing tonight, if you haven't solved this, what version of notes?

Marilyn
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
paulhollambyAuthor Commented:
NT 4.0 running Domino 5.0.8
Win 2000 running Notes 5.0.7
0
 
marilyngCommented:
Are you familiar with embedding a view?  Your detail forms can be just that, detail forms that have either a parent child relationship with the main form, or a unique id number.

The column displayed in the view can display hyperlinks that will open the detail forms for editing or the user can create a new row with the new details.  This way to have a master form, and a the ability to create dynamic subforms.

If your main document is already displaying main information, construct your view with the first column categorized according to your unique key, and then embed the view in the form.  Put a "create new" button on the master form, and then create the smaller detail forms.

Much easier in R5 than in 4.6 --

LEt me know if you understand how to do this..

Marilyn
0
 
paulhollambyAuthor Commented:
Problem that I have with an embedded view, is that on the screen, it needs to be displayed in a format that would appear on an envelope (ie multiple lines for a single address)

I am using a PAB to hold all of our clients. A client may have more than one address. I have created a second form used for data entry.

All I want to be able to do, is the user selects the address type (home, work, postal) button, and it opens a new form, gets the details from the contact form, makes changes and validates, then when the user presses the save button, it saves the data back to the contact form.
0
 
marilyngCommented:
Paul, sorry I got a bit busy.  
This is a touch complicated, because the lookup view needs to concatenate the display for the addresses, so that the first column in the view is the parent UNID, and the second is the child UNID, the third the concatenated name, address, etc.:

Col1: ParentUNID or lookup value
Col2: Child UNID
Col3: Name & @Char(13) & address & @Char(13)& @char(13)etc.

(@char(13) is line return)

So when you display the main form, the field that's displaying the addresses can simply do a @dblookup on the first column and return the third.  If the form and view is set to update automatically, then when the value is edited on the address form, the lookup values should refresh on the main form.  (especially if it's a display only field).

Question: Are the buttons specifically pointing to: Home, Work, details -- that is, can I click on the "Home" button and expect to edit only one document?

Question 2:  are you creating responses or new documents?

If you're creating responses, then the parent id is stored in the child document in the $Ref field, so by doing a lookup:
FIELD Project := @DbLookup("":""; ""; "By doc ID"; @Text($Ref); "Project");
@All

You can return all documents that belong to the parent. If you need one out of the set, then I usually create a lookup view that contains the child document with the first sorted column being:

@Text($Ref)+ documenttype,

and the second column containing the child's document unid, so I can call the specific document by its unique id.

For instance, your "Home" button would concatenate the @Text(parentdocumentunid) + "Home"
search on this value and return the child's document unid ID.  From there you can use the:

@Command( [OpenDocument] ; writeOrReadOnly ; UNID ; width : height)  where the UNID is the child UNID returned from the original search.

Does this help?




0
 
eddieluvCommented:
Hi Marilyng,

I'm quite new to Notes Development and I'm sorry that I can't fully digest your respond to the article above but I do have this similar question.

Assuming I have this Document #2 (Child) containing "Field B" whose value I inherited from another document called Document #1 (Parent). After some computation using "Field B" I came with an answer which is I stored in "Field C" of the same document as "Field B".

The question is, how do I save the data into "Field A" which is on Document #1 (Parent)?

Thanks.

Eddie
0

Featured Post

Important Lessons on Recovering from Petya

In their most recent webinar, Skyport Systems explores ways to isolate and protect critical databases to keep the core of your company safe from harm.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now