Re: Effects on RST in Calling Proc
- From: "David W. Fenton" <dXXXfenton@xxxxxxxxxxxxxxxx>
- Date: Sat, 03 Sep 2005 18:29:54 -0500
rkc <rkc@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
news:f5pSe.75699$Hx4.20168@xxxxxxxxxxxxxxxxxxxx:
> Whether or not the effects of move operations on the recordset in
> the procedure it's passed to are reflected in the calling
> procedure on return is easily tested so I assume your question is
> does it make sense to open two recordsets. I'd say no. You can
> always save your position before passing the recordset and return
> to it after the call. I believe that is a legitimate/safe use of a
> Bookmark.
I wouldn't.
I'd save the PK of the record that's current when you pass the
recordset to called procedure, then when control returns do a
FindFirst on the PK.
My rule: Never depend on bookmarks for anything where you can use
actual data to do so. Use bookmarks only for circumstances where you
*can't* use data.
--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc
.
- Follow-Ups:
- Re: Effects on RST in Calling Proc
- From: rkc
- Re: Effects on RST in Calling Proc
- References:
- Effects on RST in Calling Proc
- From: Tim Marshall
- Re: Effects on RST in Calling Proc
- From: rkc
- Effects on RST in Calling Proc
- Prev by Date: Re: Build comma-delimited list from table
- Next by Date: Re: Build comma-delimited list from table
- Previous by thread: Re: Effects on RST in Calling Proc
- Next by thread: Re: Effects on RST in Calling Proc
- Index(es):
Relevant Pages
|
