Re: UniOLEDB setup

[Simon Lewington]

Kebbon [EMAIL PROTECTED] wrote...

 Other consultants who have previously been accessing my Unidata
 5.1.3/HP/UX 11.0 data using ODBC are  now trying to do it using
 OLEDB.  Everything appears to be set  up correctly - that is the UCI
 Config file (without making any changes from the ODBC setup,  I
 presume)

Check
C:\IBM\UniDK\Config\uci.config
instead of
C:\IBM\UniClient\Config\uci.config

What with Informix/IBM and unidk/uniclient there's a lot of perms on this
one.

Simon







-- 
u2-users mailing list
[EMAIL PROTECTED]
http://www.oliver.com/mailman/listinfo/u2-users

UniOLEDB setup

[Kebbon]

Other consultants who have previously been accessing my Unidata 5.1.3/HP/UX 11.0 data 
using ODBC are now trying to do it using OLEDB.  Everything appears to be set up 
correctly - that is the UCI Config file (without making any changes from the ODBC 
setup,  I presume).  They are using a database name found in the ud_databases file 
(again, just as in ODBC).  The connection string  (live data x'd out) appears below, 
along with the resulting error message that is invariably returned.  Any suggestions 
would be greatly appreciated.
Thanks,
Kebbon Irwin

 HP9000connString = Provider=IBM.UniOLEDB;  _
   Data source=xxx;  _
   Location=xxx;  _
   User ID=xxx;  _
   Password=xxx 

Died in UCI::SQLConnect() with SQLSTATE IM976, Native error:0 [IBM][SQL 
Client]UCI connections to non UniVerse databases is not allowed
--
u2-users mailing list
[EMAIL PROTECTED]
http://www.oliver.com/mailman/listinfo/u2-users

RE: UniOLEDB setup

[Nick Southwell]

Try removing the Provider element, Its either VB6 or VB.Net that
doesn't like it from our experience.

Cheers

Nick

-Original Message-
From: Kebbon [mailto:[EMAIL PROTECTED] 
Sent: 01 April 2004 20:05
To: Info-Ardent List
Subject: UniOLEDB setup

Other consultants who have previously been accessing my Unidata
5.1.3/HP/UX 11.0 data using ODBC are now trying to do it using OLEDB.
Everything appears to be set up correctly - that is the UCI Config file
(without making any changes from the ODBC setup,  I presume).  They are
using a database name found in the ud_databases file (again, just as in
ODBC).  The connection string  (live data x'd out) appears below, along
with the resulting error message that is invariably returned.  Any
suggestions would be greatly appreciated.
Thanks,
Kebbon Irwin

 HP9000connString = Provider=IBM.UniOLEDB;  _
   Data source=xxx;  _
   Location=xxx;  _
   User ID=xxx;  _
   Password=xxx 

Died in UCI::SQLConnect() with SQLSTATE IM976, Native error:0 [IBM][SQL 
Client]UCI connections to non UniVerse databases is not allowed
-- 
u2-users mailing list
[EMAIL PROTECTED]
http://www.oliver.com/mailman/listinfo/u2-users


This correspondence is confidential and is solely for the intended
recipient(s). If you are not the intended recipient, you must not use,
disclose, copy, distribute or retain this message or any part of it. If you
are not the intended recipient please delete this correspondence from your
system and notify the sender immediately. 

No warranty is given that this correspondence is free from any virus.  In
keeping with good computer practice, you should ensure that it is actually
virus free. E-mail messages may be subject to delays, non-delivery and
unauthorised alterations therefore, information expressed in this message is
not given or endorsed by Open and Direct Group Limited unless otherwise
notified by our duly authorised representative independent of this message.

Open and Direct Group Limited is a limited company registered in United
Kingdom under number 4390810 whose registered office is at 10 Norwich 
Street, London, EC4A 1BD

--
u2-users mailing list
[EMAIL PROTECTED]
http://www.oliver.com/mailman/listinfo/u2-users