1. If you have a small project it may be easier to use different data object in each
page.
2. For a large project you have to consider the overhead of resource.
Each data object uses resources.
3. In your case I am not sure why you need to use more than one data object.
4. You only need one page to display the result. Just set up your data object
correctly from 3 different places and load the result page.
a. just clear the dynamic criteria if you want to display all.
b. set the dynamic criteria to one member and go to the display page.
c. use a search page and go to the display page.
5.
"Ray" <[EMAIL PROTECTED]> wrote:
>
>I have 3 pages that all use the same data object. One page displays all members
>using our application, another one displays properties for a specific member, and the
>third page displays members satisfying search criteria. I'm finding it very
>difficult in
>my onBeforeExecuteEvent() for the data object to keep track of which generated SQL
>I should be executing. I'm using several user session objects to:
>
>1. store a boolean value indicating whether or not to use previously saved generated
>SQL
>2. store the previous search criteria as a string
>
>Is using a single data object for several pages a good idea in general? If so, when
>do
>you draw the line and define a new one?
>
>If anyone can offer a better solution I'd sure appreciate it!
_________________________________________________________________________
For help in using, subscribing, and unsubscribing to the discussion
forums, please go to: http://www.netdynamics.com/support/visitdevfor.html
For dire need help, email: [EMAIL PROTECTED]
