RE: ODBC question on R+w and +r only. solved
Hmmm. Just gave all permisions to user, and created a NEW table database in
Access, and it imported the new permissions.
It seems that Access imports the permissions, and then doesn't let you chang
them, even when they have been changed in the pgsql system.
not a bad idea I usppose.
Now to work out the correct permissions that the ODBC driver should run under.
I notice there is [x]Read Only field in the config... should it be on/offf and
what are the ramifications of that side of it?
Great database engine by the way. especially for ease of use! in my novice
opinion anyway :-)
bob
--
http://www.chalmers.com.au. Publications From China in 24 different languages.
English, French, German, Russian, Arabic, Spanish, Chinese, Burmese, Bengali,
Hindi, Indonesian, Italian, Japanese, Korean, Portuguese, Persian, Swahili,
Sinhalese, Thai, Tamil, Urdu, Vietnamese. China Books for CIBTC, Beijing.
----- Original Message -----
From: Robert Chalmers <robert@chalmers.com.au>
To: psql-general <pgsql-general@postgreSQL.org>
Sent: Wednesday, January 20, 1999 8:51 PM
Subject: [GENERAL] RE: ODBC question on R+w and +r only. solved
Hmmm. Just gave all permisions to user, and created a NEW table database in
Access, and it imported the new permissions.It seems that Access imports the permissions, and then doesn't let you
chang
them, even when they have been changed in the pgsql system.
not a bad idea I usppose.
Now to work out the correct permissions that the ODBC driver should run
under.
I notice there is [x]Read Only field in the config... should it be on/offf
and
what are the ramifications of that side of it?
The next build of the driver will be more permissive in its defaults.
These conservitive settings go back to the days when ODBC updates were a
flip of a coin.
Import Notes
Resolved by subject fallback