| re: Rows created by a stored proc prompt Access' dreaded "write conflict"
I resolved this problem: it turned out that the PGSQL ODBC driver needed
to have "Row Versioning" checked.
Cheers,
Eric
Eric E wrote:
[color=blue]
> Hi all,
> I am using an Access 2000 client linked to a Postgresql 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 problem is that Access will not modify these records via table or
> form view (form has a DAO recordset), giving its generic "Write
> conflict: another user has modified this record" message. I can use
> forms and table view 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 kind of
> stored procedure is pretty key for us going 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[/color]
| 
