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
Other
John,
Why write a wrapper?
ED is a scrudgy BASIC program - (uv Account BP ED.B). You could just modify
that.
Brian
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of John Hester
Sent: 26 April 2004 22:22
To: U2 Users Discussion List
Subject: [UV] Problem
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 associated with them:
- you have install the trigger in all your
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
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
[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 do
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
Other things to consider:
1. What happens if someone uses XEQ within ED to edit another record.
2. What about people using UPDATE.RECORD
3. And what about REVISE (ENTRO/MODIFY)
There are many different ways to get around audit trails if people want to.
AdrianW
-Original Message-
From:
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
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-1 = id
repeat
select list to mylist
loop
readnext id else done = true
until done
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
11 matches
Mail list logo
