At least that is how I have understood SQL in the past and up until someone enlightens me. BTW I am not really "in the know" about "real" SQL! I have mostly used special "flavors" like FoxPro. Definitely not the real thing!
djl
At 12:45 PM 1/27/03 -0500, you wrote:
Hi,
This is what I'm using... and it works ok.
I guess it just seems to me that there should be a way to fetch a particular row from the results of a query without having to process the entire record set as text in MetaTalk.
I'm just confounded by the cursor API, but maybe I'm missing something. Why would I want to be able to fetch columns from the cursor but never rows?
Say I have a database cursor, and all I want to do is plunk the first 10 records, with 10 fields each, into a form. I have to make 10 calls to RevDB to fetch the columns, and then I have to merge 10 columns of text to make 10 rows. ECK! I know I can use revdb_querylist() and script around this, but then again... I want to use a database cursor!
I just don't follow the logic- why fetch columns but not rows?
Brian
� get revdb_querylist(return,comma,tConnectID,tQuery)
� put line 1 to 100 of it into tFirstResults
It ought to do the trick "when you want to obtain the
data for use but don’t need to retain a reference to
the records that the data came from."
Hope this helped,
|| Dave LeYanna ||
|| Director IS ||
|| Right to Life of Michigan ||
====================== _______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
