Hi Sim,
Thanks for the advice. The problem persists when I close and reopen
any of the objects, or even the database client. I suspect it has
something to do with how Access determines the uniqueID of the row, but
that's only because that seems to be the major issue with Access and
ODBC. Any other suggestions?
Thanks,
Eric
Sim Zacks 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.
>
> 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@postgresql.org
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
>