Re: remote view and stored procedures

From: Trey Walpole (treyNOpole_at_SPcomcastAM.net)
Date: 04/16/04 

Date: Fri, 16 Apr 2004 10:46:19 -0500

Not remote views, but buffering could still be useful for form level stuff
that catches buffer changes before navigation (i.e., "Do you want to save
changes?")

"toylet" <toylet_at_mail.hongkong.com> wrote in message
news:uEMWZa7IEHA.2144@TK2MSFTNGP12.phx.gbl...
>
> If all access to SQL server data is to be done via stored procedures,
> could one still used the remote views and buffering features provided by
> VFP?
>
> --
> .~. Might, Courage, Vision. In Linux We Trust.
> / v \ http://www.linux-sxs.org
> /( _ )\ Linux 2.4.22-xfs
> ^ ^ 9:24pm up 1:39 0 users 1.05 1.00

Relevant Pages

  • Re: anybody out there who uses Visual Foxpro on Progress (V9) data??
    ... Have you set a buffering level 3 or 5 for the view. ... With 3, row buffering, the update occurs whenb you move off the row in the ... the connection and driver are working as expected and the problem would more ... >> It is a remote view on a single table. ...
    (microsoft.public.fox.programmer.exchange)
  • Re: Remote view / cursor oddity
    ... I don't see what buffering has to do with my problem. ... If nothing is open in the data session, and 'track' is a remote view ... USE track IN 0 ALIAS track_curs ... instead of opening a 'track' cursor and inserting into that. ...
    (microsoft.public.fox.programmer.exchange)
  • Re: Remote view / cursor oddity
    ... 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 ... > * since when it completes there is no alias 'track' open. ...
    (microsoft.public.fox.programmer.exchange)
  • Re: Detecting clsoed socket on OutputStream.Write
    ... What causes this 'expected behaviour' to 'fail' is TCP asynchronous writing and buffering. ... If the write to the socket just goes into your local send buffer and the remote close hasn't already been detected, ... It's only when you write *after* the remote close has been detected that you can get an IOException, and this in turn can only happen if there was data still pending to be written when the remote closure occurred. ...
    (comp.lang.java.programmer)