Symeon,
The data type is 'date'. I have not tried any other data type. Maybe I should
change the sql data type to 'datetime'?
Rudy
Message: 9
Date: Sat, 5 Nov 2011 11:31:29 -
From: Symeon Breen syme...@gmail.com
To: 'U2 Users List' u2-users@listserver.u2ug.org
Subject: Re: [U2] BCI
2011 17:37
To: 'u2-users@listserver.u2ug.org'
Subject: Re: [U2] BCI
?Symeon,
The data type is 'date'. I have not tried any other data type. Maybe I should
change the sql data type to 'datetime'?
Rudy
Message: 9
Date: Sat, 5 Nov 2011 11:31:29 -
From: Symeon Breen syme...@gmail.com
To: 'U2
1st problem - - the data type - is a date or datetime - have you tried the
other - or even a timespan.
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Cooper, Rudy
Sent: 04 November 2011 22:02
To:
I have not found any way to force SQL type compatibility, but I have
worked around it by using CAST/CONVERT in the SQL statement to make
UniData see the data as a type it did recognize. In my case it was a
matter of BigInt not being handled (which is ironic, since U2 doesn't
usually fuss
Thank you David. I suspected I might be reduced to trying a cast on the server
side. I should also mention that I am using the Easysoft driver and I've
posited the question to them, just to see their take.
Kind regards!
-- Original message --
From: David Beahm [EMAIL
Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ray Wurlod
Sent: Sunday, January 02, 2005 11:01 PM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] BCI Connect
A couple of small things.
You didn't need SQLNumResultCols, because you already knew - from your
SELECT
or either.
- Original Message -
From: [EMAIL PROTECTED]
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] BCI Connect
Date: Wed, 28 Jun 2006 07:38:35 +0100
Does anyone know if I can call a SQL stored procedure using the
SQLExecDirect command?
Thanks
Graham
---
u2
@listserver.u2ug.org
Subject: RE: [U2] BCI Connect
Graham,
By any chance are you doing BCI via UNIX?
Cheers,
Angelo Collazo
System Administrator
Silver Line Building Products Corporation
One Silver Line Drive
North Brunswick NJ, 08902
[EMAIL PROTECTED]
Ph: 732.435.1000 X4495
-Original Message-
From
We had problems with it too, when I did a BCI app - the way I found it
worked was to use VAR char for everything, on the SQL side, and it
worked!!!
-Original Message-
From: Cooper, Rudy [mailto:[EMAIL PROTECTED]
Sent: Friday, May 26, 2006 3:45 PM
To: u2-users@listserver.u2ug.org
Subject:
Rudy ..
I've already ran it thru IBM and they tell me it is a problem on the sql
server side.
they would .. wouldn't they
I have a uv program that inserts into a table in sql server via a stored
procedure. I get the following error:
lExecute Error, state 37000 Natcode 201
Errtxt
Rudy
What does your code look like?
BTW...You should use SQLExecDirect when calling stored procedures, when
it doesn't need to be called repeatedly (as it is supposedly more
efficient). Check out the online help or BCI manuals for more info.
Here's a snippet of source code from a real sample of
into
my UV program from a stored procedure.
Any suggestions would be greatly appreciated.
Thx,
Rudy
Date: Thu, 16 Mar 2006 23:14:44 +1100
From: Hona, David S [EMAIL PROTECTED]
Subject: RE: [U2] bci
Rudy
What does your code look like?
BTW...You should use SQLExecDirect when
Rudy,
Looking at your UV BASIC BCI code and stored procedure, I suggest the
following:
A) I noticed that your stored procedure has 9 arguments, not 8 as you've
defined in your BCI code. You've ommitted the most important one - the
output argument. Isn't that what you're asking about?
B) I
SQLBindParameter is for binding a variable to a parameter marker in the query
to be executed.
What you really need is SQLBindCol, which binds a variable to a column in the
result set.
If the number of return columns is N, you need N invocations of SQLBindCol
(that is, you must consume all the
Hi Wendy
I'm able to use BCI (UniBasic SQL Client Interface) with one statement
environment, but when I try to add a second one it stops working.
It has been while since I worked with BCI, but I am sure that you have to
reset the sqlallocstmt for each query.
Regards
David Jordan
---
On 2/8/06, David Jordan [EMAIL PROTECTED] wrote:
I'm able to use BCI (UniBasic SQL Client Interface) with one statement
environment, but when I try to add a second one it stops working.
It has been while since I worked with BCI, but I am sure that you have to
reset the sqlallocstmt for each
Thanks for your help. As far as I can tell, I allocating a new
statement for each one:
STATEMENT = 'update ...'
STATUS-1 = SQLAllocStmt(connection.env,update.stmt.env)
STATUS-1 = SQLExecDirect(update.stmt.env,STATEMENT)
STATEMENT = 'select * from ...'
STATUS-1 =
On 2/8/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
is the update section returning
a value which you need for the query section? Is something running
after the update section before the query that is needed for the query
section?
No. That was lifted straight from a little test program
Hi Wendy
Could you not do that as one SQL statement ie as below
UPDATE .. WHERE ID = (SELECT id FROM table WHERE ...)
Regards
David Jordan
Managing Consultant
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
For UniVerse at least you can have as many statement environments as you like
in a connection environment. Of course each must have its own management space
allocated (SQLAllocStmt).
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit
On 2/8/06, David Jordan [EMAIL PROTECTED] wrote:
Could you not do that as one SQL statement ie as below
UPDATE .. WHERE ID = (SELECT id FROM table WHERE ...)
No. That's stripped down from the actual code until I can figure out
what I'm doing wrong.
The original program selects a
The command HELP BCI SQLBindParameter refers to DATEFORM and
SQLSetConnectOptions, and to Appendix A (of the BCI manual). Looking at all of
those you may get a clue, though as far as I can make out, DATEFORM is not
supported for ODBC dbms types in 10.0. Anyway take a look; I'll take a look at
David,
I'm on the road (as usual), doing non-UniVerse stuff. The earliest I will get
to take a look at this is next weekend. Since you have a workaround, I guess
the urgency's gone. Have you contacted IBM support? (And what version of SQL
Server are you using?)
Regards,
Ray
- Original
BCI mimics the ODBC API, so dates are expected to be in ODBC format
(-MM-DD).
Using the constant SQL.B.DATE in SQLBindParameter() or SQLBindColumn() causes
an implicit conversion to occur, so that you get internal format out of a
SELECT, and must supply internal format in bound variables
]
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] BCI Connect
Date: Fri, 31 Dec 2004 07:55:00 -
Ray Richard
Thanks for you reply. Here is my code which works, but would appreciate if
you could cast a quick eye over it.
029: * use Unidata Connect to get data from Siebel
030: $INCLUDE
Integration
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ray Wurlod
Sent: 31 December 2004 06:02
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] BCI Connect
Source code for the CONNECT verb is supplied. Track it down and take a look
at it.
The steps
Source code for the CONNECT verb is supplied. Track it down and take a look at
it.
The steps are as follows. You should check for, and clear, errors at every
step. Seriously. ODBC simply does not function with dirty handles.
1. Allocate ODBC environment (SQLAllocEnv)
2. Allocate
27 matches
Mail list logo
