I have to do what you are asking a few and far between times, and I've had to slap my self on the head to remind myself that SQL-Select is not going to get it for me. So I do a scan or other such techniques.
Maybe we need a way to 'force' a reading of buffered data from a table/cursor.
Select * from qTemp_Cursor FORCED where <Such and such> Into Cursor qTemp2_Cursor
Anthony
-----Original Message----- From: Derek J. Kalweit [mailto:dkalweit at sensiblesoftware D.OT com]
Anthony:
Are you saying you never have a need to get small amounts of information from a temporary cursor being built? Say you're using a SQL Server with an invoice/item type of app. You create an invoice item(single-record remote-view, updateable cursor, whatever). You then create items for this invoice(another remote view/updateable cursor, with numerous items). Now, if you want to issue a select statement such as "SELECT SUM(nPrice) FROM rv_Items", you'll get incorrect data. This is even worse, when you load an old invoice, add a couple items, and the SUM() only sums the old items and not the new. This isn't just a problem with table buffering on DBFs, but rather buffering of any sorts on cursors.
-- Derek
©2003 Testi, Anthony L (UseTemp) |