We are using a product and just found out that one of the reasons we're
having some difficulties on an installation was that one of my dictionaries
was not defined at a new site. This caused a 'Exec' of a SELECT to fail,
but here's the kicker -- in BASIC, we could have 'seen' the error with
...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of David
Wolverton
Sent: 19 February 2010 14:49
To: 'U2 Users List'
Subject: [U2] UniObjects 'Exec'
We are using a product and just found out that one of the reasons we're
having some difficulties on an installation
We've worked around this by having another way to run screens, etc. in
a character mode. So if we're having an issue, we run the screen or
web page in this special testing mode which doesn't go to uniobjects,
but captures everything that would go there and puts it out in a log we
can read.
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of David Wolverton
Sent: 19 February 2010 2:49 PM
To: 'U2 Users List'
Subject: [U2] UniObjects 'Exec'
We are using a product and just found out that one of the reasons we're
having some difficulties on an installation was that one of my
...@listserver.u2ug.org] On Behalf Of Dianne
Ackerman
Sent: 19 February 2010 15:20
To: U2 Users List
Subject: Re: [U2] UniObjects 'Exec'
We've worked around this by having another way to run screens, etc. in
a character mode. So if we're having an issue, we run the screen or
web page in this special testing mode
: Re: [U2] UniObjects 'Exec'
David
The Command object does have a Response property which is like the THIS in
your example. But that would have to be logged in some way. Also, if you're
running UniVerse, it may create an entry in the errlog ..
Brian
-Original Message-
From: u2-users-boun
Users List'
Subject: Re: [U2] UniObjects 'Exec'
It's UniData, sadly! This is half the challenge!! They are definitely more
UniVerse developers than UniData.
However, they tell me that 'Response' does NOT contain the message I would
see in THIS -- which would be Illegal Attribute:^am:select
A try catch around the exec will capture the exception.
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of David Wolverton
Sent: 19 February 2010 14:49
To: 'U2 Users List'
Subject: [U2] UniObjects 'Exec'
We are using
-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of David A. Green
Sent: Friday, February 19, 2010 8:36 AM
To: 'U2 Users List'
Subject: Re: [U2] UniObjects 'Exec'
David,
I'm running UniData and have no issue tracking down error messages from
UniObjects. I
Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of David Wolverton
Sent: February 19, 2010 09:49 AM
To: 'U2 Users List'
Subject: [U2] UniObjects 'Exec'
We are using a product and just found out that one of the reasons we're
having some
: Friday, February 19, 2010 10:26 AM
To: U2 Users List
Subject: Re: [U2] UniObjects 'Exec'
I did some playing around with this and was surprised at what I found.
First I would have assumed that any error messages would have been returned
as part of the command.Response
But they aren't.
So I tried
11 matches
Mail list logo