|
Author:
mahesh
|
|
2010-07-30 01.42.42 |
Thanks Dale & Doug. |
|
Author:
DougCMH
|
|
2010-07-29 10.10.19 |
*RECNAME tells the DDS to return the record, field, and optionally, position
within the field, where the cursor is.
*WINDOW returns the row and column position of the cursor.
*MOUSE returns the row and column of the mouse cursor, and optionally, the row
and column at the start of a two click event, such as a drag-and-drop.
If you do not explicitly specify *WINDOW or *MOUSE, then *RECNAME is assumed.
You do not need to explicitly specify *RECNAME.
Your two examples are really the same. |
|
Author:
DaleB
|
|
2010-07-29 10.06.02 |
My bad. I looked at DDS reference. *RECNAME is optional. There is no difference
between
RTNCSRLOC (*RECNAME &RECORD &FIELD) and
RTNCSRLOC (&RECORD &FIELD)
Both RECORD and FIELD must be defined in the same record as 10A with usage H
(hidden).
Using the alternate syntax with *WINDOW or *MOUSE is when you get row and column.
Suggest you look at the DDS reference for example code. It even has a table that
shows you what values are returned, depending on where the cursor is located. |
|
Author:
mahesh
|
|
2010-07-29 09.36.36 |
Dale........ I used RTNCSRLOC with out using "*RECNAME" as RTNCSRLOC(&RECORD
FIELD); but I am able to get the field and record name.
Actually what I want to ask is: difference b/n
RTNCSRLOC (*RECNAME &RECORD &FIELD) and
RTNCSRLOC (&RECORD &FIELD)
thanks
Mahesh |
|
Author:
DaleB
|
|
2010-07-29 09.28.48 |
Depends what you want to do with the information returned by RTNCSRLOC. *RECNAME
gives you record and field names back. Without *RECNAME, you get row and column. |
|
Author:
mahesh
|
|
2010-07-29 09.11.57 |
then what is the use of keyword (*RECNAME) -- where we give "Y" for Type
indicator *RECNAME when we define return cursor location.
I am a bit confused when to give *RECNAME and when not. Please help me.
Cheers
|
|
Author:
Jadoggidin
|
|
2006-08-04 12.37.32 |
The reason you need both is because you can have multiple record formats on
the same screen at the same time. Since it's possible that fields with the
same name can exist in two different record formats on the same screen, you
need both to uniquely identify in which field the cursor is located. |
|
Author:
DougCMH
|
|
2006-08-04 05.52.18 |
That's probably why you need both.
There's an optional third parm, too - a field that contains the position within
the field that the cursor is on.
There's an alternate version that returns row and column.
All this can be found on the InfoCenter. |
|
Author:
ans
|
|
2006-08-04 05.02.07 |
for defining RTNCSRLOC keyword why we need both
Cursor record . . . . . . . . . . . . .
Cursor field . . . . . . . . . . . . . .
either of them is not enough ....
|