Re: stacked canvases vs multiple forms

Remember to consider your transaction processing. COMMIT is a form level action and will commit all DML on the entire form not just on visible stacked canvases.

So if you have independent data on your stacked canvases (i.e. save this canvas but not that one) then calling other forms may be the way you need to go.

"Timbo" <tjbacs_nospam_at_attbi.com> wrote in message news:3DAD7AC2.30206_at_attbi.com...
>
> I'm a beginner, so I very well may be missing something obvious here.
> What are advantages/disadvantages of using stacked canvases vs multiple
> forms to navigate an application?
>
> I've coded active web pages using jsp, php, asp for form data entry and
> for the most part I would have a form page, "call itself" to do field
> validation checking and to write the data to the db. Then if I had to
> do more or different processing, I would direct to another active page.
>
> What is the best way to do that using forms? With 9i, forms are
> essentially turned into jsp anyway, but this stacked canvas thing has me
> wondering.
>
> Thanks,
>
> Tim
>
Received on Thu Oct 17 2002 - 15:10:57 CEST