Guys-
I installed CSDK 3.0 with the .Net 2.0 driver on my PC (XP Service Pack 2, Microsoft Visual Studio 2005) and everything seems to work fine. The Informix native driver works and everything is happy. I installed it on an associate's computer (also XP Service Pack 2, Microsoft Visual Studio 2005) and we get an error message every time it tries to access the native driver as in this sample program:

'The Informix native client (C:\Program Files\IBM\Informix\Client-SDK\bin\netf20\IBM.Data.Informix) was added as a reference to this project.

Imports IBM.Data.Informix

Module Module1

Sub Main()
Dim thisIfxConn As New IfxConnection()

End Sub

Note that all it does is initialize the driver. No open action or anything else. The program dies right there with this error:

System.TypeInitializationException was unhandled
Message="The type initializer for 'IBM.Data.Informix.IfxConnection' threw an exception."

The "Inner Exception" is this:

{"DELIMIDENT - no error information available"}

Delimident is not set on either computer. We tried rerunning the installation to so a "repair" of the driver with no change in outcome. I didn't find any reference to driver errors in the .Net manual and the installation manual only covers a failed install. I am calling support, but I thought someone may have run into this before.

TIA, EEM



Everett E. Mills
Programmer/DBA
National Beef Packing Co., LLC.
P.O. Box 20046
Kansas City, MO 64195-0046*

Voice: (816)713-8621
Fax: (816)713-8850
E-Mail: eemills (AT) nationalbeef (DOT) com

Did you have a previous version of the ClientSDK or Informix-Connect on that
other machine ?

If so - remove both versions - reboot, then install the new version (again)-
reboot and then try again...


On Tuesday 26 June 2007 20:22, Everett Mills wrote:
--
Mike Aubury

Aubit Computing Ltd is registered in England and Wales, Number: 3112827
Registered Address : Murlain Business Centre, Union Street, Chester, CH1 1QP

Thanks Mike. Somehow he had CSDK 2.81 and CSDK 2.90.TC6 both installed
at the same time. When we installed 3.0.TC1, it happily overwrote 2.9
and started a war with the remaining 2.81 driver.

--EEM