Informix Tools and Solaris
Posted in 1998
Topics: Connectivity: ESQL/C, 4GL & Embedded SQL, Platform-Specific Issues
This is a multi-part message in MIME format. ------=_NextPart_000_001D_01BE01BD.F9C66C90 Content-Type: multipart/alternative; boundary="----=_NextPart_001_001E_01BE01BD.F9C7F330" ------=_NextPart_001_001E_01BE01BD.F9C7F330 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable We recently received 4gl & sql informix tools, Ver 7.20, for sun solaris = 2.6. I was wondering if anyone has experienced or has any ideas on what = problems we may encounter if we load/compile using these tools above on = an earlier version of Solaris (2.4 & 2.5) and not reorder for these = platforms. TIA, Lori ------=_NextPart_001_001E_01BE01BD.F9C7F330 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN"> <HTML> <HEAD> <META content=3Dtext/html;charset=3Diso-8859-1 = http-equiv=3DContent-Type><BASE=20 href=3D"file://C:\\Program Files\\Common Files\\Microsoft = Shared\\Stationery\\"> <STYLE> <!-- body, PRE, BLOCKQUOTE, a, MENU, dd, UL, DT, dir, ADDRESS, h1, h2, h3, = h4, h5, h6, HR { font-family: "Arial"; font-size: 12pt; color: 000000; } --> </STYLE> <META content=3D'"MSHTML 4.72.2106.6"' name=3DGENERATOR> </HEAD> <BODY=20 background=3Dcid:001501be01f0$44423100$6885d0cc@lcardwel.hcssa.dencom.arm= y.mil=20 bgColor=3D#ffffff> <DIV>We recently received 4gl & sql informix tools, Ver 7.20, for = sun=20 solaris 2.6. I was wondering if anyone has experienced or has any = ideas on=20 what problems we may encounter if we load/compile using these tools = above on an=20 earlier version of Solaris (2.4 & 2.5) and not reorder for these=20 platforms.</DIV> <DIV> </DIV> <DIV>TIA,</DIV> <DIV>Lori</DIV> <DIV> </DIV> <DIV> </DIV> <DIV> </DIV></BODY></HTML> ------=_NextPart_001_001E_01BE01BD.F9C7F330-- ------=_NextPart_000_001D_01BE01BD.F9C66C90 Content-Type: image/gif Content-Transfer-Encoding: base64 Content-ID: <001501be01f0$44423100$6885d0cc@lcardwel.hcssa.dencom.army.mil> R0lGODlhFAAUAPcAAP//////zP//mf//Zv//M///AP/M///MzP/Mmf/MZv/MM//MAP+Z//+ZzP+Z mf+ZZv+ZM/+ZAP9m//9mzP9mmf9mZv9mM/9mAP8z//8zzP8zmf8zZv8zM/8zAP8A//8AzP8Amf8A Zv8AM/8AAMz//8z/zMz/mcz/Zsz/M8z/AMzM/8zMzMzMmczMZszMM8zMAMyZ/8yZzMyZmcyZZsyZ M8yZAMxm/8xmzMxmmcxmZsxmM8xmAMwz/8wzzMwzmcwzZswzM8wzAMwA/8wAzMwAmcwAZswAM8wA AJn//5n/zJn/mZn/Zpn/M5n/AJnM/5nMzJnMmZnMZpnMM5nMAJmZ/5mZzJmZmZmZZpmZM5mZAJlm /5lmzJlmmZlmZplmM5lmAJkz/5kzzJkzmZkzZpkzM5kzAJkA/5kAzJkAmZkAZpkAM5kAAGb//2b/ zGb/mWb/Zmb/M2b/AGbM/2bMzGbMmWbMZmbMM2bMAGaZ/2aZzGaZmWaZZmaZM2aZAGZm/2ZmzGZm mWZmZmZmM2ZmAGYz/2YzzGYzmWYzZmYzM2YzAGYA/2YAzGYAmWYAZmYAM2YAADP//zP/zDP/mTP/ ZjP/MzP/ADPM/zPMzDPMmTPMZjPMMzPMADOZ/zOZzDOZmTOZZjOZMzOZADNm/zNmzDNmmTNmZjNm MzNmADMz/zMzzDMzmTMzZjMzMzMzADMA/zMAzDMAmTMAZjMAMzMAAAD//wD/zAD/mQD/ZgD/MwD/ AADM/wDMzADMmQDMZgDMMwDMAACZ/wCZzACZmQCZZgCZMwCZAABm/wBmzABmmQBmZgBmMwBmAAAz /wAzzAAzmQAzZgAzMwAzAAAA/wAAzAAAmQAAZgAAMwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACwAAAAAFAAUAEAIQwBJCBxI sKBBAAgTKlyYUCDDhwsdQpwoceLDihYjksh4cSNHjR9BhmzocSQAjCFRflTJkWVGlxZhUiw5UiZE gzhzBgQAOw== ------=_NextPart_000_001D_01BE01BD.F9C66C90--
Related threads
- Conversion to differeent characters sets
- Problem in changing locale via dbexport/dbimport
- Re: Matches not Work in 7.30
- DATABASE vs CONNECT TO: Invalid characters error?