Thanks to everyone for all the suggestions. Turns out the solution was
relatively simple. I just needed to use PERFORM ED instead of EXECUTE
ED to make ED run in the wrapper program's workspace. This is in PICK
flavor. Seems like I once knew the difference between EXECUTE and
PERFORM in PIC
Triggers would be nice, but the'd have to work on type19 files.
Modifying ED is simple, but you might want to wrap other verbs, so
generalized wrapper pgm is good. Protect the vanilla versions of ED,
DELETE, UPDATE.RECORD, REVISE as 'remote-controlled' R-items that will
only execute if executed b
essage-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> Behalf Of Hona, David S
> Sent: Monday, April 26, 2004 11:04 PM
> To: 'U2 Users Discussion List'
> Subject: RE: [UV] Problem reactivating select list[Scanned]
>
>
> Triggers have more overhead as
reactivating select list
I wrote a wrapper for the ED command last week to keep an audit trail of any
changes made to files outside our applications. I'm just writing a before
and after version of an edited record to a temp file and comparing
afterwards. All seemed fine until one of my cowo
It appears that ED is aware of an active select list 0, even when it is not
using it. Interesting behavior - is this a bug or feature? Well, in
INFORMATION flavour accounts - at least!
In INFORMATION flavour, when you 'X' out, this appears to kill the active
select list 0. Hence, upon the next in
+61 8 8408 4273 - Work
+61 417 268 665 - Mobile
+61 8 8408 4259 - Fax
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of [EMAIL PROTECTED]
Sent: Tuesday, 27 April 2004 11:29 AM
To: [EMAIL PROTECTED]
Subject: RE: [UV] Problem reactivating select list
esday, April 27, 2004 3:40 PM
To: U2 Users Discussion List
Subject: RE: [UV] Problem reactivating select list
Have you thought of using trigger subroutines to keep the audit trail?
Much easier, and the before- and after-records and keys are available for
you right there in the arguments. :D
-
Have you thought of using trigger subroutines to keep the audit trail?
Much easier, and the before- and after-records and keys are available for you right
there in the arguments. :D
--
u2-users mailing list
[EMAIL PROTECTED]
http://www.oliver.com/mailman/listinfo/u2-users
April 2004 9:12 AM
>To: U2 Users Discussion List
>Subject: Re: [UV] Problem reactivating select list
>
>[EMAIL PROTECTED] wrote:
>
>>
>> John what is wrong with this approach
>> loop
>>readnext id else done = true
>> until done do
>>list<
You're not wrong. Triggers on files came in at rev 10.
--
Regards,
Clif
On Apr 26, 2004, at 18:21, John Hester wrote:
Correct me if I'm wrong, but on UV 9.6 I think I'd have to convert
every UV file to a SQL table to be able to use a trigger.
--
u2-users mailing list
[EMAIL PROTECTED]
http://
You might try this. I am not on a system right now, so I can't test
this until later.
--
Regards,
Clif
~~~
W. Clifton Oliver, CCP
CLIFTON OLIVER & ASSOCIATES
Tel: +1 619 460 5678Web: www.oliver.com
~~~
saveList
: John Hester [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 27 April 2004 05:22
To: U2 Users Discussion List
Subject: [UV] Problem reactivating select list
I wrote a wrapper for the ED command last week to keep an audit trail of
any changes made to files outside our applications. I'm just writ
" PASSLIST ID.LIST
AdrianW
-Original Message-
From: John Hester [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 27 April 2004 05:22
To: U2 Users Discussion List
Subject: [UV] Problem reactivating select list
I wrote a wrapper for the ED command last week to keep an audit trail of
any change
Humm...got me there...don't know when they added the ability to create
Triggers on Non-SQL tables?
> Correct me if I'm wrong, but on UV 9.6 I think I'd have to
> convert every
> UV file to a SQL table to be able to use a trigger.
>
__
This
Mark Eastwood wrote:
Have you looked at "Triggers" ?
I wrote a wrapper for the ED command last week to keep an
audit trail of
any changes made to files outside our applications. I'm just
writing a
before and after version of an edited record to a temp file and
comparing afterwards.
Corr
[EMAIL PROTECTED] wrote:
John what is wrong with this approach
loop
readnext id else done = true
until done do
list<-1> = id
repeat
select list to mylist
loop
readnext id else done = true
until done do
execute "ed ":file:" ":id
repeat
then before, after, between the two loops you can d
In a message dated 4/26/2004 5:22:07 PM Eastern Daylight Time, [EMAIL PROTECTED]
writes:
> I wrote a wrapper for the ED command last week to keep an audit trail of
> any changes made to files outside our applications. I'm just writing a
> before and after version of an edited record to a temp
Have you looked at "Triggers" ?
>
> I wrote a wrapper for the ED command last week to keep an
> audit trail of
> any changes made to files outside our applications. I'm just
> writing a
> before and after version of an edited record to a temp file and
> comparing afterwards.
>
_
I wrote a wrapper for the ED command last week to keep an audit trail of
any changes made to files outside our applications. I'm just writing a
before and after version of an edited record to a temp file and
comparing afterwards. All seemed fine until one of my coworkers
informed me he could
19 matches
Mail list logo
