VW + Mac OS X + ODBC

Hi, is there any user of VisualWorks and Mac OS X Leopard and ODBC?

If I try to ODBC connect, this error occurs:
-----
Unhandled exception. Database client libraries are inaccessible.  
Either the Object Engine has not been linked with the required  
libraries, or the DLLs for those libraries are not in your search  
path...
-----

Whats wrong? Thanks, pf

Is it typical problem with odbc library names which are platform  
dependent? (eg. libodbc.so.1 vs odbc32.dll vs libiodbc.2.dylib...)
Unfortunately, I can't find any library configuration in classes from  
ODBCEXDI package (parcel).
There is also ODBCUnixSupport package in cincom public repository -  
but no luck with it.

My config: Mac OS X Leopard, VW NC 7.6 dev feb 02

Thanks for help, pf

On 9.2.2008, at 1:49, Petr Fischer wrote:

had similar problems with oracle libraries(but on tiger). You need have
the right library in Your DYLD_LIBRARY_PATH.
but this can be tricky after apple discovered security problems with
dynamically loaded libraries.
http://docs.info.apple.com/article.html?artnum=305509
regards
manfred

On Feb 9, 2008, at 1:49 AM, Petr Fischer wrote:

I changed library file in DLC C Connect Window from odbc32.dll to  
libiodbc.2.dylib (class ODBCCLIInterface).

I am able to get some error messages from Firebird SQL Database with  
"tricky" datasource name (DSN=xxx):

connection := ODBCConnection new
username: 'sysdba';
password: 'masterkey';
environment: 'DSN=MY_FIREBIRD_ODBC_DSN';
connect.

But ODBC interface doesn't work (error reading data form connection  
errors etc.). Changing library name in DLL C is probably not  
sufficient. For example: ODBCCLINTInterface subclass (for Windows NT?)  
is full of C definitions. The problem is probably not only about ODBC  
libraries - it may require more work in smalltalk api (I don't know  
exactly).

pf

On 15.2.2008, at 11:26, Manfred Kohl wrote: