Comments on: SQL Select – Bufferred Queries

By: Anonymous

Anonymous — Sun, 08 Jul 2007 00:44:00 +0000

Here is the discussion about Buffering = .t. on UT I was talking about http://www.universalthread.com/wconnect/wc.dll?2,15,1136588

By: Nadya

Nadya — Fri, 06 Jul 2007 17:08:00 +0000

We tried to use it, but found it extremelly slow in a long and complex procedure, so we had to resort to dbase commands (locate/seek) instead for our purpose. I’ve documented this in one of my posts in UT.

By: Mike Potjer

Mike Potjer — Thu, 05 Jul 2007 17:42:00 +0000

I find it extremely useful as well. One use that comes to mind is being able to display subtotals while the user is still editing the data which affects the totals, such as when creating or updating a budget in our accounting software. This allows a user to play with the numbers and view the results before actually committing them to the table.

By: V Salem

V Salem — Wed, 04 Jul 2007 03:37:00 +0000

Absolutely, I use this method as well, and I find this feature incredibly useful, I also use this to check if the user has selected some records before saving and then if they wish to select other records the “already selected records” get excluded. If we didn’t have this feature we would have to use the getnextmodified to build a cursor manually, I previously had to do this using the getnextmodified and it was a pain.