Re: Rows created by a stored proc prompt Access' dreaded "write conflict"

From: Jeff Eckermann <jeff_eckermann(at)yahoo(dot)com>
To: Sim Zacks <sim(at)compulab(dot)co(dot)il>, pgsql-general(at)postgresql(dot)org
Cc: Eric E <whalesuit(at)bonbon(dot)net>
Subject: Re: Rows created by a stored proc prompt Access' dreaded "write conflict"
Date: 2004-11-02 14:23:26
Message-ID: 20041102142326.78488.qmail@web20824.mail.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


--- Sim Zacks <sim(at)compulab(dot)co(dot)il> wrote:

> After the stored procedure is run, call requery on
> the form that was
> updated.
>
> We are in the middle of moving Access
> implementations to PostGreSQL.
> I'd be happy to trade war stories, if you'd like.

I hope that you do it on the list, so that the rest of
us can profit from your experience.

>
> Thank You
> Sim Zacks
> IT Manager
> CompuLab
> 04-829-0145 - Office
> 04-832-5251 - Fax
>
>
________________________________________________________________________________
>
> Hi all,
> I am using an Access client linked to a PG 7.4
> server via ODBC.
>
> I have a stored proc on the server that inserts rows
> into a
> table.particular table, accomplished via an INSERT
> within the body of the stored proc. The procedure
> does not explicitly
> commit this data, as no transactions are invoked.
>
> The problem is that Access will not modify these
> records via table or
> form view, giving its generic "Write conflict:
> another user has modified
> this record" message. It does just fine for any
> other records in the
> table, but it will not modify those created by the
> stored proc. It will
> also execute an UPDATE OR DELETE query to modify
> these records This
> stored procedure is pretty key for us to go forward.
>
>
> Does anyone have any ideas of what's going on and
> how to fix it? I can
> post more details, but I wanted to see if this was a
> known problem
> before doing so.
>
> Many thanks,
>
> Eric
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to
> majordomo(at)postgresql(dot)org
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 2: you can get off all lists at once with the
> unregister command
> (send "unregister YourEmailAddressHere" to
> majordomo(at)postgresql(dot)org)
>


__________________________________
Do you Yahoo!?
Check out the new Yahoo! Front Page.
www.yahoo.com

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Sim Zacks 2004-11-02 14:41:01 Re: Rows created by a stored proc prompt Access' dreaded "write conflict"
Previous Message Eric E 2004-11-02 14:19:22 Re: Rows created by a stored proc prompt Access' dreaded "write conflict"