Hi Wade, ODBC flag in the open functions is "o" and not "q" (PDF book has a typo). I do not think the Linux binaries have ODBC built-in. You should build your ODBC unicon yourself using gcc and the make scripts provided in the unix config directory.
The last revision of the interface uses: - f:=open(.."o"..) to open an ODBC connection - fetch(f) to fetch a row - sql(f,command_string) to send SQL statements to the server - close(f) to close the connection dbopen, dbfetch and dbclose are obsolete and got removed from my page. Some links at unicon page may still be outdated though. We'll try to fix it asap. I presume you also installed an ODBC driver for PGSQL right? I am not sure when you visited my page. I am updating the information at http://www.cs.utsa.edu/~fbalbi/unicon Federico On Tue, 2 Oct 2001, Wade Bowmer wrote: > Could I have some direction here, please. I would like ODBC to work in > Unicon and I think I've got all the bits together, but Unicon is giving me > an odd error. > > 1. I'm on RedHat 6.2 > 2. I'm using PostGres. It has a much nicer CLI client than MySQL. > 3. iODBC is installed. > 4. All access is entirely local. > 5. open(..., "q", ...) [as per the .pdf] fails at runtime with a "dbm > database expected" error > 6. open(..., "o", ...) [as per Frederico's web page] fails at runtime with > a "invalid second argument to open" error > 7. dbopen(...) [well, I thought it was worth trying] fails with a > "procedure or integer expected" error showing it's not defined. > 8. I'm using the 10.0 beta binary of Unicon. > 9. I think I have the odbc.ini files correct, but there are no tools I can > find to test them. I intend to try from my Windows machine, though. > 10. The target database exists. > > What am doing wrong? Is ODBC not provided in this binary? > > Wade. _______________________________________________ Unicon-group mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/unicon-group
