Hi Sunny,
Are you doing it as a subroutine call or an execute?
If a subroutine call hits an input (eg record locked), it never comes back.
We wrap subroutine calls around an execute for this reason.
Execute should come back, with appropriate status (waiting for input, buffer
full, or at end
We had a similar problem.
What happened with us, is when we passed a date through,
it changed the date into American Format and not the
format is was given as.
The way we got around this is when we connect to UniVerse Server,
execute the command: DATE.FORMAT ON
I now do this as a rule.
Check date conversion routines (if you pass the date in output format). If
you system is set to use European date format when the program is called
from uniObjects the process would use American date format.
Serguei
- Original Message -
From: Sunny Matharoo [EMAIL PROTECTED]
To:
Some little traps.
The Subroutine has to be catalogued for uniobjects else the call returns
nothing, where you could call it from tcl without it being catalogued.
Sometimes if the subroutine returns an unassigned variable, then it can
cause uniobjects to abort.
Regards
David Jordan
---
Sunny,
Hi. I second the point made about the inadvertant date conversion
(sorted by a one line execute in your called subroutine). I 'inherited'
a VB app that uses the subroutine object: interestingly, one of my
predecessors had set the call in the code, and if the returned error
property wasn't
to the code Simon has inherited we time the query and if it runs in
under 10 seconds run it again.
Peter Welsh
Senior IT Development Officer
NHSAC
-Original Message-
From: Simon Carter [mailto:[EMAIL PROTECTED]
Sent: 10 August 2005 11:36
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] Failure
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bjorn Behr
Sent: Wednesday, 10 August 2005 20:14
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] Failure of UniObjects subroutine call
We had a similar problem.
What happened with us, is when
