[AccessD] Write Conflict SQL and adp

Can you bookmark, refresh, and the recordsetclone.findfirst to get back to
the orignal record?

ROcky

Original Message:
-----------------
From: David Emerson newsgrps at dalyn.co.nz
Date: Wed, 24 Jun 2009 10:00:09 +1200
To: accessd at databaseadvisors.com
Subject: Re: [AccessD] Write Conflict SQL and adp


Tried this with no success.

I do note that if I refresh the form data after changing a record I 
can change it again but this is not a good solution as the current 
record then becomes the first one.

David

At 24/06/2009, you wrote:
>Just put it in your code where you are exiting a control. Or in the
>oncurrent if you want.  Anywhere you want where your records becomes
"dirty"
>and you want to ensure it is written away before doing anything else.
>
>You might have a text control called "My Commission" and on the OnExit you
>might put.
>
>Me.dirty = false
>Me!MyCommission = me!MyCommission * 10000
>Me.dirty = false
>
>Stick it anywhere you want.  The me. Refers to the form you are currently
>in.
>
>Max
>
>
>
>-----Original Message-----
>From: accessd-bounces at databaseadvisors.com
>[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of David Emerson
>Sent: 23 June 2009 20:06
>To: Access Developers discussion and problem solving
>Subject: Re: [AccessD] Write Conflict SQL and adp
>
>Max,
>
>Can you please expand on your suggestion.  How do you use
>me.dirty=false to force it to write edits away?
>
>David
>
>At 22/06/2009, you 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


--------------------------------------------------------------------
mail2web.com – Enhanced email for the mobile individual based on Microsoft®
Exchange - http://link.mail2web.com/Personal/EnhancedEmail