Re: Humbled: Informix SE & Win95 ODBC?

Keith Sharp wrote in message <01beee94$acd82710$9e10a8a5@emc2369>... >There are tools in the informix start menu which will help you. It is Find >error, run ilogin using the parameters set in setnet32. The run finderr to >get detail on the error on possible resolutions. Also make sure you have >your sql socket set in /etc/services, and that service is set in >$INFORMIXDIR/etc/sqlhosts. > >Chris Wood <cwood@xmission.com> wrote in article ><37C1D0F4.A80ED20F@xmission.com>... >> I have been humbled by my attempt to get ODBC's working on Win95 to my >> Informix SE database. It always says it can't find the service in >> /etc/services. On a Windows-95 system the services file is C:\\WINDOWS\\SERVICES Be sure that the service name you use in SetNet32 or the ODBC driver configuration is defined in that file. >> Other than running the setup.exe for Informix Client SDK, are there >> supposed to be any environment var or directories and files created on >> the client pc to make it work? Installing Client-SDK will normally create a directory such as C:\\INFORMIX (or whatever you choose at install time) with a load of sub-directories and files beneath it. >> Also, my Informix Client does NOT list the protocol that the Unix >> install process told me to use for my server. It said to use "setlitcp" >> which is not an option on the client ODBC software. Windows clients *always* use soctcp. For connecting to a Unix SE database choose sesoctcp. The soc/tli issue is platform local and describes the local api to use to access the TCP/IP layer. On Unix this may be socetc or TLI depending on platform, on Windows it is always sockets (i.e. Winsock). Chris