[AccessD] Write Conflict SQL and adp

rockysmolin at bchacc.com rockysmolin at bchacc.com
Mon Jun 22 07:34:53 CDT 2009


David:

I had this problem recently with an Access FE/BE.  The problem occurred on
a subform which had as its record source a query which included a table
that was also included in the record source of the main form.  

IIRC, the solution turned out to be requerying the main form from the
subform.

But I don't know if your app has the same condition.

HTH

Rocky


Original Message:
-----------------
From: David Emerson newsgrps at dalyn.co.nz
Date: Mon, 22 Jun 2009 20:46:19 +1200
To: accessd at databaseadvisors.com
Subject: [AccessD] Write Conflict SQL and adp


I have an SQL2005 BE and Access XP adp FE.

The database is used to track stock for a number 
of locations.  Each stored procedure has a filter for location

Most of the record sources are stored procedures 
that combine multiple tables (the extra tables 
are for sorting the records - for example a 
products table is joined to the inventory table 
so that the inventory can be sorted by product order).

I have the unique tables set where I can, and the

I am getting a "write conflict - This record has 
been changed by another user 
  " error when I 
try to change a record a second time when it is displayed in a continuous
form.

I have tried Googling.  The main solution is to 
include a timestamp field in every table.  This I have done with no joy.

Any thoughts on what I should look for?  Should I 
be looking at the SQL security setting for roles?


Regards

David Emerson
Dalyn Software Ltd
Wellington, New Zealand 


-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com


--------------------------------------------------------------------
mail2web - Check your email from the web at
http://link.mail2web.com/mail2web






More information about the AccessD mailing list