> This -Bsymbolic option is great news! Yes, indeed, go ahead and dust
> the _SQL stubs in results.c!
OK, I've got some cleaned-up code now. The only outstanding issue I can
recall is whether CommLog and Debug should absolutely not be allowed in
the user-accessible .odbc.ini file. btw, I've now realized that the
driver information is not in the database-specific area as I might have
claimed earlier, but in another area ([Default]) of the .odbc.ini file.
I suspect that differences in behavior between the Unix iODBC driver and
the drivers you work with on Windows boxes have lead to some of our
confusion over where things should go. In fact, it appears that the
iODBC driver manager does not know about an odbcinst.ini file of any
sort, so the .odbc.ini file is the only one which is very useful under
Unix.
So, the CommLog/Debug question seems to have only one answer for Unix
installations (they must be allowed somewhere in odbc.ini) but we could
disable that for non-Unix builds. Or, replace references to odbcinst.ini
with odbc.ini for Unix installations.
The current status is that the code compiles and runs, allowing full
access to databases. I haven't gotten the time type to display properly
yet (it shows today's date also) but that may be a problem with
ApplixWare.
> Byron (minus one pair of tonsils)
Ouch :(
- Tom
