| T.R | Title | User | Personal Name
 | Date | Lines | 
|---|
| 641.1 | /SHOW | UTRTSC::BOSMAN | We're just sugar mice in the rain | Thu May 07 1992 11:01 | 8 | 
|  |     Hi,
    
    Could you try (I only use the first letters):
    
    /VALID = de.dn
    /SHOW  = ".dn ' ' fe.fn[.dfn]"
    
    Sjaak.
 | 
| 641.2 | extended problem | NBOIS::MARSING | Gerhard Marsing      @NBO | Thu May 07 1992 12:48 | 14 | 
|  | 
thanks,
this implied nested for loop is a solution, but now i want to use it 
in an index form, so i have to built a phantom dataset with this data, 
so i have to do a "real" join to get a new table (like a view in rdb).
any other solution around in shrinking human digital skills pool ?
is there any further solution in combination with SRA (stand. 
Rel.Access) Asset ? i want to access rdb data.
mercy,Gerhard Marsing
 | 
| 641.3 | SRA, SRA, SRA, SRA!! | SHALOT::LANPHEAR | Test the water or turn the tide? | Thu May 07 1992 14:11 | 11 | 
|  |     Hello Gerhard,
    
      Since Joe Duncan hasn't responded (he's not here this week), and I
    happen to sit next to his cube, I'll add his emphasis that yes, you
    want to go with SRA.  Definitely.  Better than that sliced stuff.
    
      Especially for Rdb data.  For example, on a form, Joe just told me
    last week that you can use /TABLE, /FIELDS and /JOIN to really make 
    things work the way you want.
    
    						Cheers, acting Joe, Dan'l
 | 
| 641.4 | /alias? | IOSG::CARLIN | Dick Carlin IOSG, Reading, England | Thu May 07 1992 14:43 | 6 | 
|  |     To produced your "joined" index you may be able to use the /alias
    directive to derive the function_name from the function_nr. I seem to
    remember doing a similar thing in the past. I can't remember the exact
    details, but I'll try an experiment when I get time.
    
    Dick
 | 
| 641.5 | /AlIAS, as Dick said | IOSG::ALLAN | Derek, DTN 830-3669 | Thu May 07 1992 18:28 | 16 | 
|  | 	Dick is right. If I understand your example properly your index form
        would be scrolling a phantom bound to your department data-set. One
        of the FMS fields in your display would be called DEPART_NAME in order
        to pick up the corresponding data-set field. The other field in your
        index could be called anything, but would be qualified by
        /ALIAS ="FUNCTION_ENTRY.FUNCTION_NAME[.DEPART_FUNCTION_NR]"
                                              ^
	Note the dot          ................|
        Inside the /ALIAS qualifier you can use the .FIELD syntax to obtain
        the value of the field inside the record being scrolled, and thus use
        it to key into another data-set as above.
	Cheers,
	Derek
 | 
| 641.6 | SRA knows relational algebra | SHALOT::DUNCAN | Joe - CIS/EIC Doc. Mgmt. Solution Set Consultant | Mon May 11 1992 16:31 | 15 | 
|  |     Gerhard,
    Since what you want to do is do a join of two tables (which I assume
    are in and Rdb/VMS database, because of your comment in .2), I would
    definitely recommend considering using VAX SQL Relational Access for
    ALL-IN-1.  If your join is one that you will be doing over and over
    again, then you could create a view in the Rdb database, and then
    access the view using an SRA entry form.  SRA allows you to add
    criteria to be used against views, if these vary at run-time.  Since
    you are in Europe, contact your local ASSETS library for SRA.  In the
    U.S., the proper procedure is to contact the Cross-Industries EIC.  For
    more information on SRA, check out the notes conference, SHALOT::SRA.
    Joe Duncan @ OPA
    
 |