Date: Mon, 3 May 2004 10:18:30 -0500
From: Bruno Wolff III <bruno@wolff.to>
To: Simon Dobie <simon@auditbureau.org.au>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: FIXED  Problems when using MS Access to display
Message-ID: <20040503151830.GA23846@wolff.to>
Mail-Followup-To: Simon Dobie <simon@auditbureau.org.au>,
	pgsql-interfaces@postgresql.org
References: <40958AAA.30707@auditbureau.org.au>
	<4095E59C.9040904@auditbureau.org.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4095E59C.9040904@auditbureau.org.au>
User-Agent: Mutt/1.5.6i

On Mon, May 03, 2004 at 16:24:28 +1000,
  Simon Dobie <simon@auditbureau.org.au> wrote:
> Its ok, i managed to figure it out. the Primary Key was not being  
> updated (i did make it auto update in postgress but it doesnt seem to 
> auto update) so i had to manually change the unique value for the 
> records (which was the same for each one.)

There is no auto update in Postgres. If you are talking about the serial
type, it is important to know that it works by having a function get a
value from a sequence as a default action. If you actually provide a
value for this column when inserting a row, that value will get used
instead of using the default action to get a value.

If you still have questions about this, if you describe precisely what you
are doing we might be able to shed more light on what is happening.