Hi, Kevin. Shaun wasn't reporting a problem. He was answering my questions
about his trigger that does what I'm trying to do.
Kevin King-2 wrote:
Shaun, have you checked the trigger code on that file?
___
U2-Users mailing list
Thanks for the info, Shaun.
Shaun.Ferguson wrote:
HP Itanium
UniData Release 7.1
Basictype p
Records cannot be deleted from TCL (ECL?) even with a select list
active:
1 records selected to list 0.
DELETE COUNTY
Do you want to delete records in select list?(Y/N) Y
'KEY':cannot be
HP Itanium
UniData Release 7.1
Basictype p
Records cannot be deleted from TCL (ECL?) even with a select list
active:
1 records selected to list 0.
DELETE COUNTY
Do you want to delete records in select list?(Y/N) Y
'KEY':cannot be deleted, due to trigger constraint.
Shaun, have you checked the trigger code on that file?
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
Hi, all. I'm new to this forum, but have been programming multivalue database
apps for years. I ran across something here that really has me puzzled. I
wonder if anyone has seen something like this and might be able to shed a
bit of light as to what's happening.
I'm running Unidata 6.0 on hpux.
Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of jonathanm
Sent: Thursday, April 21, 2011 11:03 AM
To: u2-users@listserver.u2ug.org
Subject: [U2] Very Weird Trigger Behavior
Hi, all. I'm new to this forum, but have been programming
...@listserver.u2ug.org] On Behalf Of jonathanm
Sent: Thursday, April 21, 2011 11:03 AM
To: u2-users@listserver.u2ug.org
Subject: [U2] Very Weird Trigger Behavior
Hi, all. I'm new to this forum, but have been programming multivalue database
apps for years. I ran across something here that really has me puzzled. I
@listserver.u2ug.org
Subject: [U2] Very Weird Trigger Behavior
Hi, all. I'm new to this forum, but have been programming multivalue
database
apps for years. I ran across something here that really has me puzzled. I
wonder if anyone has seen something like this and might be able to shed a
bit of light
, 2011 11:27 AM
To: 'U2 Users List'
Subject: Re: [U2] Very Weird Trigger Behavior
I would change the SELECT to an XLATE command.
David A. Green
(480) 813-1725
DAG Consulting
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf
AM
To: dgr...@dagconsulting.com; U2 Users List
Subject: RE: [U2] Very Weird Trigger Behavior
I think this was a check to prevent deletion of a CODE_DEFS record if in use
in the TRADES file, so XLATE wouldn't help.
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2
...@listserver.u2ug.org] On Behalf Of jonathanm
Sent: Thursday, April 21, 2011 11:03 AM
To: u2-users@listserver.u2ug.org
Subject: [U2] Very Weird Trigger Behavior
Hi, all. I'm new to this forum, but have been programming multivalue
database
apps for years. I ran across something here that really has me
To: 'U2 Users List'
Subject: Re: [U2] Very Weird Trigger Behavior
I would agree -- if there is an active select list, then you would get some
seriously unexpected behavior doing another select unless you 'pushed' that
new select to a different 'List ID' than the default '0' list -- just ensure
it's
On 4/21/2011 11:03 AM, jonathanm wrote:
Hi, all. I'm new to this forum, but have been programming multivalue database
snip
I really need to have it perform the intended check before deletion. Any
ideas?
Your execute of the SELECT will potentially result in an active select
list that doesn't
...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Israel, John R.
Sent: Thursday, April 21, 2011 9:52 AM
To: 'U2 Users List'
Subject: Re: [U2] Very Weird Trigger Behavior
Not knowing the size of the original files, as long as they are not too big,
adding an index just to get
: [U2] Very Weird Trigger Behavior
Then there is the possibility of adding another trigger to the update of the
TRADES file that builds a CODES.XRF cross reference file. You avoid the large
nothing index, gives you a straight READ, plus it's an easy rebuild program.
-Original Message-
From
Subject: Re: [U2] Very Weird Trigger Behavior
On 4/21/2011 11:03 AM, jonathanm wrote:
Hi, all. I'm new to this forum, but have been programming multivalue database
snip
I really need to have it perform the intended check before deletion. Any
ideas?
Your execute of the SELECT will potentially
Thanks, all. A few things I've observed:
1. It doesn't matter what type of command is being EXECUTEd; the problem
persists. I've tried the suggestions here, plus unrelated commands such as
DATE or WHERE. It seems that anything EXECUTEd will cause the ID to be
lost because the process is, I
-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of jonathanm
Sent: Thursday, April 21, 2011 11:25 AM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] Very Weird Trigger Behavior
Thanks, all. A few things I've observed:
1. It doesn't matter
: Thursday, April 21, 2011 11:57 AM
To: U2 Users List
Subject: Re: [U2] Very Weird Trigger Behavior
On 4/21/2011 11:03 AM, jonathanm wrote:
Hi, all. I'm new to this forum, but have been programming multivalue
database
snip
I really need to have it perform the intended check before deletion. Any
ideas
Nice catch, Wally. It appears to work for a UniBasic DELETE, but definitely
not for the ECL DELETE.
I suppose that is because the UniBasic runtime environment does not share
its symbol table with the shelled EXECUTEd environment, so overwriting
system variables (ID, filename) doesn't matter. Is
Subject: Re: [U2] Very Weird Trigger Behavior
Nice catch, Wally. It appears to work for a UniBasic DELETE, but definitely
not for the ECL DELETE.
I suppose that is because the UniBasic runtime environment does not share
its symbol table with the shelled EXECUTEd environment, so overwriting
system
We are doing this with a county and zip file - the trigger is on the
county file and a record cannot be deleted if it's referenced in the zip
file:
SUBROUTINE TRIG.COUNTY.DEL (EXECSTAT, DICTFLAG, FILENAME, COUNTY_ID)
EQU DELETE_DENIED TO 0
EQU DELETE_ALLOWED TO 1
EXECSTAT = DELETE_DENIED
IF
Of
shaun.fergu...@ferguson.com
Sent: Thursday, April 21, 2011 3:42 PM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] Very Weird Trigger Behavior
We are doing this with a county and zip file - the trigger is on the
county file and a record cannot be deleted if it's referenced in the zip
file:
SUBROUTINE
Wally Terhune-2 wrote:
Uh, don't grant your users ECL access? :-)
I've often said the computer system would work fine if we could keep people
off of it.
Wally Terhune-2 wrote:
Feel free to submit this request via your U2 support provider. Not sure
how easily it could be accomplished,
Wow! This is really similar to what I'm trying to do. What is your: OS,
Unidata version, BASICTYPE?
Also, are you having success with both ECL DELETEs and UniBasic DELETEs?
Thanks!
Jonathan
Shaun.Ferguson wrote:
We are doing this with a county and zip file - the trigger is on the
county
Good word of caution, John. Thanks.
Israel, John R. wrote:
The one risk I see here is if you are at TCL and have a bunch of keys in
an active select that you are going to delete. If THAT select list is not
loaded into one of the higher active select buffers (i.e. 1-9), you will
have some
26 matches
Mail list logo
