Re: stacked canvases vs multiple forms

In fact you COULD build a whole application in 1 BIG Form. This has several disadvantages:
- the form itself contains simply 'to much to control' -> you loose oversight
- the form-save/compile etc. takes longer and longer - for each block the underlying table MUST exist in the database, so if there are
tables which you don't need you still have to create them because your big form
relies on it somewhere.

From my point of view you have to take a paper and divide you application in modules (functional blocks).
Each block you implement as 1 form. inside a form you use canvases to implement the 'local' functionality

Some guidelines (rougly): NOTE: you CAN create many more

-on 1 form I would say a maximum of 10 datablocks is the limit.
-10 (stacked) canvases is also max.
- forms filesize: i would say : 1 megabyte maximum

Good luck!

Stephan

"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 - 22:57:13 CEST