Re: Remote view / cursor oddity
- From: "Fred Taylor" <ftaylor@xxxxxxxx!REMOVE>
- Date: Tue, 24 Jan 2006 18:51:09 -0700
If you're using a remote view, there is an implied buffering mode in effect.
If you move the record pointer in the view, any changes in that record in
the view will be applied to the "source" table. Tha's the way row buffering
works. If you don't want any changes to be applied to the source table
until you're ready to do a TABLEUPDATE(), you'll have to swith to table
buffering.
--
Fred
Microsoft Visual FoxPro MVP
"Jack Jackson" <jacknospam@xxxxxxxxxxxxxxx> wrote in message
news:sc7dt19t93mfa8hjhai9369julgfvbtdf1@xxxxxxxxxx
>I just ran into something that I don't understand. VFP 8 SP1,
> although I doubt that matters.
>
> With nothing open in the data environment, open a remote view:
>
> USE track IN 0 ALIAS track_curs
> * At this point 'track_curs' is the only thing open.
>
> * The following statement apparently reads data from track_curs,
> * since when it completes there is no alias 'track' open.
> SELECT * FROM track WHERE ... INTO CURSOR xxx
> * At this point 'track_curs' and 'xxx' are open.
>
> * Likewise, the following statement inserts into track_curs:
> INSERT INTO track .....
>
> If the initial USE is removed, the SELECT will silently open the
> remote view 'track' and leave it open, and the INSERT will insert into
> that remote view, which is the expected behavior.
>
> Is inserting into the alias when the remote view name is used the
> expected behavior? It seems wrong to me.
.
- Follow-Ups:
- Re: Remote view / cursor oddity
- From: Jack Jackson
- Re: Remote view / cursor oddity
- References:
- Remote view / cursor oddity
- From: Jack Jackson
- Remote view / cursor oddity
- Prev by Date: Re: rich text control crashing
- Next by Date: Re: Non-standard Characters
- Previous by thread: Remote view / cursor oddity
- Next by thread: Re: Remote view / cursor oddity
- Index(es):
Relevant Pages
|