David Emerson
newsgrps at dalyn.co.nz
Tue Jun 23 14:01:10 CDT 2009
Thanks for everyone's suggestions - working through them now. Arthur - I replaced the sproc with a view. This worked when I hardcoded the location into the select statement. However I need to use a parameter for filtering (not sure if you can do this with views). Here is an example of a sproc: ALTER PROCEDURE [dbo].[spfrmLAWSDensity] ( @Location varchar(50) ) AS SET NOCOUNT ON; SELECT dbo.tblLAWSDensity.* FROM dbo.tblContainer INNER JOIN dbo.tblLAWSDensity ON dbo.tblContainer.ContainerID = dbo.tblLAWSDensity.ContainerID WHERE dbo.tblContainer.Location = @Location ORDER BY dbo.tblLAWSDensity.DateFrom, dbo.tblContainer.ListOrder Even though the view worked, if I hardcode the location into the sproc and remove the parameter I still get my error. David At 22/06/2009, you wrote: >Something else that you may want to try, David -- replace the stored >procedure with a view that does the same Select and then try to edit the >same row twice. >A. > >On Mon, Jun 22, 2009 at 5:07 AM, Max Wanadoo <max.wanadoo at gmail.com> wrote: > > > David, just a stab in the dark, but it sounds as if it hasn't written away > > the previous edit you made on the same machine. > > > > I often use me.dirty=false to force it to write edits away. > > > > Max > > > > > > -----Original Message----- > > From: accessd-bounces at databaseadvisors.com > > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of David Emerson > > Sent: 22 June 2009 09:46 > > 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 > > > > -- > > AccessD mailing list > > AccessD at databaseadvisors.com > > http://databaseadvisors.com/mailman/listinfo/accessd > > Website: http://www.databaseadvisors.com > > >-- >AccessD mailing list >AccessD at databaseadvisors.com >http://databaseadvisors.com/mailman/listinfo/accessd >Website: http://www.databaseadvisors.com