IT is kind of a 99% of the time vs. 1% of the time. 99% of the time I like
the behavior, 1% I need it to do something that I, and I guess the designers
of VFP-SQL think so also, is odd, that is read from 'dirty' records, it does
not work like I want it to. That is why I am thinking that some sort of
switch could be added to allow for reading of dirty data. I have a hunch it
would not be easy to do, having to force the SQL engine to read buffered
data.
As the say, write a function, then to your main line code it will look like
one line.
Derek, in the apps you are working with it may be a situation that you cross
on a daily bases, in my case it is a once in a year or two problem. Take my
idea and send it to MS, then both of us will program happily every after....
Anthony
-----Original Message-----
From: Derek J. Kalweit [mailto:dkalweit (at) sensiblesoftware .DO.T com]
What's the use of a SQL engine if I can't use it to access all my anywhere?
I shouldn't have to do a SCAN when I should be able to do the same thing
with a simple(or maybe not so simple) SELECT statement. Things that would
normally take 1 SQL command turn into huge functions(SELECT WHERE IN() kinda
stuff, for example).
--
Derek
©2003 Testi, Anthony L (UseTemp) |
