D
David Lemieux
Hi,
I passed around ten hours on this one: we have a SQL
Server 2000 station, to which about 20 client connects to
via an ADP solution (Access 2003).
When inserting with conflict, some users goes through our
error handling procedures and get the SQL Server default
message (ex: violation of primary key). But there are some
who don't have this message and believe their inserts all
went fine, but there is no data inserted.
I checked on the non working stations if I would get an
error inserting the row manually via Access (in the Tables
section). I tried to append: same behavior! No insert and
no messages!
It makes me believe that it's an SQLOLEDB issue... else I
really don't know! Some are working, some are not! They're
WIN XP based, with Access 2003 with the same locals! Some
were reinstalled a short while ago, and even among them I
have successes and failures!
Please help I'm tearing my hairs on this one!
I passed around ten hours on this one: we have a SQL
Server 2000 station, to which about 20 client connects to
via an ADP solution (Access 2003).
When inserting with conflict, some users goes through our
error handling procedures and get the SQL Server default
message (ex: violation of primary key). But there are some
who don't have this message and believe their inserts all
went fine, but there is no data inserted.
I checked on the non working stations if I would get an
error inserting the row manually via Access (in the Tables
section). I tried to append: same behavior! No insert and
no messages!
It makes me believe that it's an SQLOLEDB issue... else I
really don't know! Some are working, some are not! They're
WIN XP based, with Access 2003 with the same locals! Some
were reinstalled a short while ago, and even among them I
have successes and failures!
Please help I'm tearing my hairs on this one!