× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Michael,

For what you are going for, I think different forms may be best. You can 
get the B,C, etc. forms to inherit values by checking "Formula inherit 
values from selected document" and having the field name of the field you 
want to carry over as the computed or default value of the field of the 
(B, C) form. In a view, sort by this ID Number.

Why one type is selected over another is, as you say, dependant on what 
the developer wants to do, what they prefer doing, and what is needed. If 
your documents are to be related, but not overly dependant, I think 
different forms is best.

Brian




"Michael Naughton" <michael_naughton@xxxxxxxxxxxx> 
Sent by: domino400-bounces+bmoore=averittexpress.com@xxxxxxxxxxxx
01/23/2006 09:46 AM
Please respond to
Lotus Domino on the iSeries / AS400 <domino400@xxxxxxxxxxxx>


To
"Lotus Domino on the iSeries / AS400" <domino400@xxxxxxxxxxxx>
cc

Subject
Web Development: One Form or Mulitiple Forms?






I'm looking for opinions on this. I'm about to develop an application in
which users will create documents using form A, and then optionally create
related (not response) documents based on forms B, C, etc. Some of the
information from form A will need to be duplicated on the other forms, and
all the related documents will share a common id number (key). All of this
will be done via web browsers.

I'm kind of new to Domino development, but I've got a lot of experience in
"traditional" programming. In that world, this would be a no-brainer --
I'd create a different file for each form, and I'd link them together as
necessary to show the common information.

But Domino seems to be different, and the web aspect adds another
difference. In some apps, I've seen the developer create one big form
incorporating A, B, C, etc., and just show or hide the different sections
as appropriate. In other apps I've seen the developer create different
forms and duplicate the information across all of them.

Is there a "best practice" here, or is it just a case of "it depends" or
"whatever floats your boat"?

TIA for any thoughts you might share. . . .

Mike Naughton
Senior Programmer/Analyst
Judd Wire, Inc.
124 Turnpike Road
Turners Falls, MA  01376
413-863-4357 x444
mnaughton@xxxxxxxxxxxx

_______________________________________________
This is the Lotus Domino on the iSeries / AS400 (Domino400) mailing list
To post a message email: Domino400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/domino400
or email: Domino400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/domino400.




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.