Re: Multiple Forms (OPEN_FORM vs. CALL_FORM)

From: Archana Agarwal <aagarwa2_at_osf1.gmu.edu>
Date: 1997/01/24
Message-ID: <5caja8$jnp_at_portal.gmu.edu>#1/1


Hi:
 For multiple form application, if you are accessing different tables then according to forms manual it is better to use open_form with session mode set to SESSION. This way one can save formB without saving formA as formB would be opening in new session.Plus, you can skip the default validation of call_form command.

I hope this helps

Pankaj
pgarg_at_ahcpr.gov

Gronwald (gronwald_at_aol.com) wrote:
: Let's say a user is entering in data in Form A and NOT all required fields
: have been filled in, then the user wants to open Form B and add a new
: lookup code to use when returning to Form A. They save their change in
: Form B. What is supposed to happen to Form A if we used a CALL_FORM or,
: if we used an OPEN_FORM? Since not all the required fields have been
: filled in in Form A, won't the save fail?
 

: I have read the manuals and done some testing. For the most part, a
: CALL_FORM seems to work fine, but the manuals state in black and white
: that a post will perform 'default' validation on all open forms! So,
: doesn't that mean Form A would fail validation and the save would fail?
: It doesn't in OUR tests.
 

: And what about OPEN_FORM? I must admit we haven't used OPEN_FORM much,
: but we may need to use it a lot more in the very near future. Has anyone
: effectively used OPEN_FORM in a multi-form application??? The manuals say
: that this is the 'recommended' way to 'open' forms, but this seems to open
: another can of worms...
 

: Any comments on this would be great! Thanks in advance,
 

: Dan Gronwald
: Almedica Technology Group, Inc.
: Parsippany, NJ
: dgronwald_at_almedica.com
Received on Fri Jan 24 1997 - 00:00:00 CET

Original text of this message