Tom,

I would second Rachel's observation. I rarely utilize scrolling regions anymore.
There is so much information that I can display now (in 7.6 and up) in a 
VariableListView
(such as background colors, images) that it is my preferred control now.

Jan
  ----- Original Message ----- 
  From: Rachael Malberg 
  To: RBASE-L Mailing List 
  Sent: Friday, April 04, 2008 9:55 AM
  Subject: [RBASE-L] - Re: Order for a slave scroll


  I gotta tell ya Tom, I too started off with same idea of using a scroll for 
informative child data but have dropped that method for a variable list view 
because the users can sort any of the list view columns and a double click eep 
to open the detail form.  The list view is really slick plus don't have to 
include the child table as a form table, just a where statement for the list 
that is ..
  where ChildTableForiegnKey = .FormPrimaryKeyVariable
  and you can have as many list as you like.

  Have a Fabulous Day!
  Rachael M.
  Freelance Developer
  www.DragonflyDevelopmentMN.com
    ----- Original Message ----- 
    From: Tom Frederick 
    To: RBASE-L Mailing List 
    Sent: Friday, April 04, 2008 11:36 AM
    Subject: [RBASE-L] - Order for a slave scroll


    Started adding a scroll within a form for a slave table. The data is 
entered elsewhere and the scroll is simply informational. A button is included 
to allow the user to go off to the detail if they want. Works great and the 
users like it. Two questions:

     

    1. Is there a way to use the ORDER BY command for that slave based scroll?

    2. Can there be more than one unrelated slave scroll, each using separate 
ORDER BY commands in the same form?

     

    Unrelated slave scrolls without ORDER BY work fine, but getting separate 
ORDER BYs to work is tapping the edge of my current understanding in R:Base V8.

     

    Tom Frederick

    Elm City Center

    1314 W Walnut

    Jacksonville, IL  62650

    Off - 217-245-9504

    Fax - 217-245-2350

    Email - [EMAIL PROTECTED]

    Web - www.elmcity.org

     

Reply via email to