I've discovered that if there is any change to the ODBC driver or such,
Access needs to relink tables to take effect. Not sure if it is the case
here, but wouldn't hurt to try... Was the ODBC driver updated or reinstalled
with the upgrade? Check to make sure the Read Only boxes were unchecked?
Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
----- Original Message -----
From: "Tom Lane" <tgl@sss.pgh.pa.us>
To: "Jack" <jack@antyspam.pl>
Cc: <pgsql-general@postgresql.org>
Sent: Monday, October 09, 2000 11:39 PM
Subject: Re: [GENERAL] PostgreSQL 7.0
> "Jack" <jack@antyspam.pl> writes:
> > I have been upgrading Postgresql version from 6.5 into 7.0 and slight
> > problems emerged, probably due to my insufficient knowledge:
> > 1. In the older version, in psql, I could repeat SQL commands by means
of
> > up-down keys - now I have to type everything again;
>
> Sounds like psql was built without libhistory. If you compiled postgres
> yourself, the odds are that the problem is you don't have the libhistory
> devel RPM installed. Install it, reconfigure and recompile postgres.
>
> > 2. ODBC driver I have used to cooperate with the older Postgresql
version
> > (access to the database from Access97) - now tables can be opened only
in
> > the read-only mode.
>
> Not sure about this one. The usual Access issue is that it doesn't
> like tables without primary keys, but I don't see why there'd be
> any change across postgres versions. Any ideas out there?
>
> regards, tom lane
