[AccessD] Keeping place after requerying

Rocky Smolin - Beach Access Software bchacc at san.rr.com
Thu Jun 19 22:44:17 CDT 2003


Bruce:

I think I wrote too fast.

I save the PK of the record before the one to be deleted.  Then I do the
delete and requery.  Then I use Me.RecordsetClone.FindFirst on the saved PK.
Then do Me.Bookmark = Me.RecordsetClone.Bookmark.

I think that works.

Rocky

----- Original Message ----- 
From: "Bruce Bruen" <bbruen at bigpond.com>
To: <accessd at databaseadvisors.com>
Sent: Thursday, June 19, 2003 4:35 PM
Subject: RE: [AccessD] Keeping place after requerying


> Rocky,
>
> Bookmarks are invalid after a Requery
>
> Bruce
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin
> - Beach Access Software
> Sent: Friday, June 20, 2003 1:48 AM
> To: accessd at databaseadvisors.com
> Subject: Re: [AccessD] Keeping place after requerying
>
>
> Selina:
>
> When I need to do this I save a value or combination of values that
> makes the record unique.  Then after the Requery I use RecordsetClone
> and Bookmark to move back to the desired record. If I delete a record, I
> save the fields of the previous or following record.
>
> HTH
>
> Rocky
>
> ----- Original Message ----- 
> From: "Selina Iddon" <selina at easydatabases.com.au>
> To: <accessd at databaseadvisors.com>
> Sent: Thursday, June 19, 2003 6:47 AM
> Subject: Re: [AccessD] Keeping place after requerying
>
>
> > Hi Gustav
> > When I delete a record it puts #DELETED# across all the fields.  I
> > requery it so that they don't see this. Thanks
> > Selina
> >
> > ----------------------------------------------------------------------
> > ----
> --
> > ---- Selina Iddon selina at easydatabases.com.au Ph: 0414 225 265 Easy
> > Access Databases
> > ----- Original Message -----
> > From: "Gustav Brock" <gustav at cactus.dk>
> > To: <accessd at databaseadvisors.com>
> > Sent: Thursday, June 19, 2003 5:26 PM
> > Subject: Re: [AccessD] Keeping place after requerying
> >
> >
> > > Hi Selina
> > >
> > > > I understandably annoyed customer because everytime they delete
> > something
> > > > from their very long list and the data is requeried (via code),
> > > > they
> end
> > up
> > > > at the top of their list again and have to scroll down. Can anyone
>
> > > > please help in how I keep the focus on the next record to
> the
> > one
> > > > they have just deleted?
> > >
> > > Why do you requery the form? That shouldn't be necessary - except
> > > for an unbound form ...
> > >
> > > /gustav
> > >
> > > _______________________________________________
> > > 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
>
> _______________________________________________
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>




More information about the AccessD mailing list