From: <hak...@mp...> - 2005-01-17 11:32:27
|
Hi Jeff, The problem was that libodbcinst was not among the linked libraries. When I compiled unixODBC it was named libodbcinst, not libodbcinst.so.=20 So when a configured MDBTools it could not be found and hence not linked=20 (no errors though). I created a symlink called libodbcinst.so,=20 configured and compiled MDBTools again. This solved the problem. Thanks!! /H=E5kan Jeff Smith wrote: >The only way to get the error... > > =20 > >>Could not find Database parameter, SQL state 08001 in SQLConnect >> =20 >> > >should be the entry having an empty Database parameter ("Database =3D") >or not having a Database parameter at all. As your entry seems to >have a valid Database parameter, one thing I can think of is that >there is another 'MSAccess-dummy' entry that is being picked up, >perhaps from the user's .odbc.ini file. > >Another (remote) possibility may be that libodbcinst was not picked >up when you were configuring/compiling. Do an >'ldd $YOUR_MDBTOOLS_PATH/lib/libmdbodbc.so' and see if libodbcinst >is in the list of linked libraries. If not, that may be a problem. > > =20 > >>I downloaded the latest sources from MDBTools repository and used the=20 >>following configuration: >> =20 >> > >By this, I assume you mean the MDBTools' CVS repository. > > -- Jeff Smith > >__________________________________________________ >Do You Yahoo!? >Tired of spam? Yahoo! Mail has the best spam protection around=20 >http://mail.yahoo.com=20 > =20 > --=20 M.Sc. H=E5kan Str=F6berg Marquardt & Partners AB M=E4ster Samuelsgatan 9 111 44 STOCKHOLM Tel. 08 - 440 36 75 Mobil 0709 - 46 68 79 Fax. 08 - 440 36 71 |