> Why do you want to do this? There are a couple of problems I see with this approach
> 1) Even if you could get an access ODBC driver to work on SUSE, you have the network path issue
> problem which is a pain to get working even in a pure windows environment.
> 2) Access 97 is a wee bit obsolete - that doesn't matter too much here I guess - but it is 3
> versions behind (there is Access 2000, Access 2002, and Access 2003 that all came after it).
> -- Getting back to some solutions --
> 1) It is much easier to get Access to talk to PostGres than it is to get Python/Unix to talk to
> Do you have the option of just moving all your access data to PostGres, replacing the access
> tables with linked PostGres tables and install a Pg ODBC driver on your windows 2000 pc. The
> forms etc. should pretty much work as is except for some case-sensitive issues, which I think
> there are workarounds for.
Just to add, before you try anything else, check your pg_hba.conf file to besure that you have
correctly set permissions to allow clients to connects to your database. Next verify that clients
can connect. You can use the PGODBD driver to test the connection. Once this is verified you
should have not problem connecting with Access using the ODBC driver.
Richard Broersma Jr.
In response to
pgsql-odbc by date
|Next:||From: Hiroshi Inoue||Date: 2006-11-07 01:10:18|
|Subject: Re: Fwd: Bug#396218: bind.c: bad handling of SQL_LEN_DATA_AT_EXEC|
|Previous:||From: Peter Eisentraut||Date: 2006-11-06 19:46:15|
|Subject: Fwd: Bug#396218: bind.c: bad handling of SQL_LEN_DATA_AT_EXEC breaks passing char buffer length at SQLExec time|