main logo
Subject: RE: Anomaly with buffered data and sql
Author: "Derek J. Kalweit"
Posted: 2003/07/31 14:22:00
 
View Entire Thread
New Search


> >> This means if you have views, or updateable cursors, you can't use
> >> SQL commands to read the data from them for any purpose. Bummer,
> >> eh?

> Assuming sample data in SET PATH
>=20
> SELECT * from customer WHERE "p" $ Company INTO CURSOR=20
> CurTest READWRITE
> REPLACE ALL title WITH "Alpo"
> SELECT TOP 5 * from curTest ORDER BY company
>=20
> .... gives me 5 records with "Alpo" for Title
>=20
> So READWRITE cursors are selectable, it's the buffering that
> interferes:
>=20
> * continuing...
> SELECT curTest
> CURSORSETPROP("Buffering",5, "CurTest")
> REPLACE ALL title WITH "zippo"
> SELECT TOP 5 * from curTest ORDER BY company
>=20
> .... gives me 5 records still with "Alpo" for Title.

I'm sorry Steve, I must have been unclear. I'm talking about =
remote-views, or cursors that have been made updateable to a base =
table/SQL server, such as with Paul McNett's "MakeUpdateble.prg" or =
whatever(I never used the PRG, but have done the cursorsetprop()'s =
manually in prototyping)... All of these use buffering(table buffering =
usually makes the most sense).


--=20
Derek


 
©2003 Derek J. Kalweit
<-- Prior Message New Search Next Message -->