[AccessD] Write Conflict SQL and adp

It is not the sequencing that is the problem (although if the user 
adds a new record then the refresh will sort it into its proper order 
which may not be at the end of the records).  The problem with 
refresh is that if you are working on record 6 and then tab to go to 
the next record then the records refresh and the cursor is not on 
record 1 (not 7).
David

At 24/06/2009, you wrote:
>The sequencing will depend on your dataset order. It has nothing to do with
>saving/writing the data.  If you change the field that orders the table then
>of course it will change, if you don't, then it should stay the same.
>
>Max
>
>
>
>-----Original Message-----
>From: accessd-bounces at databaseadvisors.com
>[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of David Emerson
>Sent: 23 June 2009 23:00
>To: Access Developers discussion and problem solving
>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