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
@listserver.u2ug.org'
Subject: [U2] BCI
Need some help on using a bci function with sql server.
We are running UV 10.3.3 on windows 2003 server sp2.
We've been using bci to run sprocs in sql server.
A couple of things came up that we're having problems with which we have
never used before and thought
Hello everyone, I am trying to use this and I am coming up with the error when
I try to run the SQLConnect command. The error is sqlstate = 08003, which I
have looked up and found it means the connection is not open. What I don't know
is how to go about opening the connection. I have not been
about whether something is a string or a number). I don't
know if that is going to work for your situation, though.
HTH,
David Beahm
Date: Fri, 13 Jul 2007 05:43:44 -0600
From: Trey Miller [EMAIL PROTECTED]
Subject: [U2] BCI Interface
Hello,
I'm on a system running UniData 6.0.
I'm attempting
Hello,
I'm on a system running UniData 6.0.
I'm attempting to use the BCI to return an SQL table from a 2003 MsSql
server. I've established a connection and can execute the SQLExecDirect
with a select * from tablename against several tables with no issue, but
any table which includes a
usually fuss about whether something is a string or a number). I don't
know if that is going to work for your situation, though.
HTH,
David Beahm
Date: Fri, 13 Jul 2007 05:43:44 -0600
From: Trey Miller
Subject: [U2] BCI Interface
Hello,
I'm on a system running UniData
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
: [U2] BCI
Hello List,
I have a problem with the bci inserting into sql server. I'm running UV
10.1.10, W2K Sp2.
I've already ran it thru IBM and they tell me it is a problem on the sql
server side.
Here is my problem:
I have a uv program that inserts into a table in sql server via
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
Hello List,
I have a problem with the bci inserting into sql server. I'm running UV
10.1.10, W2K Sp2.
I've already ran it thru IBM and they tell me it is a problem on the sql
server side.
Here is my problem:
I have a uv program that inserts into a table in sql server via a stored
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Cooper, Rudy
Sent: Saturday, 11 March 2006 9:48 AM
To: u2-users@listserver.u2ug.org
Subject: [U2] bci
Can someone familiar with bci assist me with one of the functions.
I'm running bci from w2k UV 10.1.10
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
Can someone familiar with bci assist me with one of the functions.
I'm running bci from w2k UV 10.1.10.
I'm trying to get a varchar output parameter from a sql server stored
procedure. I made sure the sproc worked in sql analyzer before
attempting to use bci.
In UV I can execute the
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.
The manual says You allocate the SQL statement environment with the
SQLAllocStmt function. This function allocates memory for an SQL
statement environment and
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
:[EMAIL PROTECTED] On Behalf Of David Tod Sigafoos
Sent: Tuesday, 29 March 2005 2:49 AM
To: Ray Wurlod
Cc: u2-users@listserver.u2ug.org
Subject: Re[2]: [U2] BCI and Dates to SqlServer
Ray,
sorry to do this again but i forgot to mention ..
if i change the 'prepare' section as noted here .. it does
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
: Re[4]: [U2] BCI and Dates to SqlServer
David,
How is it going?
I have done that .. been moving stuff around just to see what might correct
the problem.
According to a note from IBM .. the binding really only connects position
with var name. Actual data doesn't take effect until the execute
Ray,
if you get a chance could you please look at the sample code I sent.
I can not find any errors in it and yet the dates do not work.
According to the manual ..
If you use SQL.B.INTDATE, the SQL Client Interface assumes the program
variable holds a date in UniVerse internal date format and
Ray,
sorry to do this again but i forgot to mention ..
if i change the 'prepare' section as noted here .. it does work well.
Now I can modify the read, write shells to force the conversion ..
but now am really interested in why i am not getting it right to
begin with g
*if
Message -
From: David Tod Sigafoos [EMAIL PROTECTED]
To: Ray Wurlod [EMAIL PROTECTED]
Subject: Re[2]: [U2] BCI and Dates to SqlServer
Date: Mon, 28 Mar 2005 08:49:27 -0800
Ray,
sorry to do this again but i forgot to mention ..
if i change the 'prepare' section as noted here .. it does
Can you re-send the sample code? I seem to have deleted it already.
Thanks,
Ray
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
What happens if you replace SQL.B.INTDATE with SQL.B.BASIC in the
SQLBindParameter call?
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
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
Ray,
Thursday, March 24, 2005, 1:52:39 PM, you wrote:
RW BCI mimics the ODBC API, so dates are expected to be in ODBC format
(-MM-DD).
yes ..
RW Using the constant SQL.B.DATE in SQLBindParameter() or
RW SQLBindColumn() causes an implicit conversion to occur, so that
RW you get internal
Ray,
Thursday, March 24, 2005, 1:52:39 PM, you wrote:
snip
as further follow up here is a sample routine and info. Note that
that the only problem shows up after the sqlExecute .. and it is
caused by the write ..
RUN DAVES.BP DATE_TEST.MV
]
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
Hello all
I am trying to extract data from an Oracle Database from Unidata. I have read
through the BCI Connect manual and it looks fairly simple using the Connect
command, but much more complicated using directly within Unibasic. Does
anyone have a simple example of executing a SQL statement and
]
To: u2-users@listserver.u2ug.org
Subject: [U2] BCI Connect
Date: Thu, 30 Dec 2004 13:30:39 -
Hello all
I am trying to extract data from an Oracle Database from Unidata. I have read
through the BCI Connect manual and it looks fairly simple using the Connect
command, but much more
We are trying to congigure and use BCI on Universe 10 on a solaris 8. We
have configured Datadirects ODBC drivers properly and are able to connect to
our Oracle databases. However when we log into Universe and use the CONNECT
command we are able to connect but we get a core dump when we try to
42 matches
Mail list logo
