T24: Deletion of values
165 views
Skip to first unread message
Sridhar
Feb 7, 2011, 12:54:06 PM2/7/11
to jB...@googlegroups.com
Hi ,
I need to update the @ id ( transaction id ) of security application in LD application when an LD id is chosen.from drop down on a local field. This should happen at the time of authorization and am able to achieve it.
Say, suppose i choose LD********** id in the security appln, the @id of this security appln has to be updated in a local field in LD.
After authorization, when I amend the record and do not select the same LD id, after authorization, the previously updated field in
LD should be deleted.
I am little confused how to do this. Can anyone suggest solution for this.
I need to update the @ id ( transaction id ) of security application in LD application when an LD id is chosen.from drop down on a local field. This should happen at the time of authorization and am able to achieve it.
Say, suppose i choose LD********** id in the security appln, the @id of this security appln has to be updated in a local field in LD.
After authorization, when I amend the record and do not select the same LD id, after authorization, the previously updated field in
LD should be deleted.
I am little confused how to do this. Can anyone suggest solution for this.
Srinivas
Feb 8, 2011, 1:40:00 PM2/8/11
to jb...@googlegroups.com
Dear,
After authorization when you amend the reocrd , R.OLD of that field will hold the last LD id and read the LD record & delete the updated field with security id
Regards,
Srinivas.
--
Please read the posting guidelines at: http://groups.google.com/group/jBASE/web/Posting%20Guidelines
IMPORTANT: Type T24: at the start of the subject line for questions specific to Globus/T24
To post, send email to jB...@googlegroups.com
To unsubscribe, send email to jBASE-un...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/jBASE?hl=en
--
Regards,
SrinivasYadav. G
Mobile No: 00966 - 540625165
VK
Feb 9, 2011, 3:07:14 AM2/9/11
to jBASE
Hi,
don't forget to lock LD$NAU record, otherwise - if somebody is editing
that very record at the same time - your changes will be lost after
commit.
You need to understand what to do if that record is already locked by
somebody else.
You also need to use F.LIVE.WRITE instead of F.WRITE to update audit
trail correctly.
The whole idea of storing cross-references in core application is not
very good one. You can easily create L-type local application and
write your cross-references there without any harm.
VK
> >http://groups.google.com/group/jBASE?hl=en- Сакриј наведени текст -
>
> - Прикажи текст између наводника -
don't forget to lock LD$NAU record, otherwise - if somebody is editing
that very record at the same time - your changes will be lost after
commit.
You need to understand what to do if that record is already locked by
somebody else.
You also need to use F.LIVE.WRITE instead of F.WRITE to update audit
trail correctly.
The whole idea of storing cross-references in core application is not
very good one. You can easily create L-type local application and
write your cross-references there without any harm.
VK
>
> - Прикажи текст између наводника -
Reply all
Reply to author
Forward
0 new messages