Scott
I kinda understand more about what your saying now. I'll
have to do some experimentation to really figure out what
I am capable of doing with this.
As far as the record set creation I guess this is really
an ADO thing. While ADO gives you a lot of capabilities and
information about the database/environment when you create
the Connection object, my understanding is that when you
poll this object with the ConnectionObject.Execute method
creates a record set object behind the scenes just to be
able to execute your statement. If I did this:
ConnObj.Execute "SELECT (CVAL('Version')) FROM Sys_Tables WHERE LIMIT =
1"
then I am creating a record set, although small I still
think there are better ways of doing this.
I have some digging to do. I wish I had this book I
referencing with me... It's at home on the nightstand.
Thanks for all the info on this
Jim Limburg
Scott Salisbury wrote:
>
> Jim Limburg wrote:
>
> > In looking at the sys_Tables I don't see this information
> > like this in the table, so how does this pull this kind of
> > info.. Out of thin air or ???
>
> Jim, This is no different than doing:
>
> SELECT 'Jim Limburg' FROM Sys_Tables WHERE LIMIT = 1
> It will return your name even though you are not listed anywhere
> in the Sys_Tables table. You can SELECT anything, not just
> columns. Try my SELECT statement at the R> and see.
>
> This is also similar to what I always used to do with CHOOSE
> boxes to create menus on the fly.
>
> CHOOSE vr FROM #VALUES FOR +
> '1 First Choice ' FROM x WHERE LIM = 1 UNION SELECT +
> '2 Second Choice ' FROM x WHERE LIM = 1 UNION SELECT +
> '3 Third Choice ' FROM x WHERE LIM = 1 UNION SELECT +
> '4 Exit / Quit ' FROM x WHERE LIM = 1 +
> AT CENTER CENTER TITLE 'Title' +
> CAPTION 'Caption' LINES 6 FORMATTED
>
> Notice that we're selecting a literal text string in this case
> as well. "x" is just a dummy table with one record in it.
> CREATE TABLE x (x TEXT(1))
> INSERT INTO x (x) VALUES ('x')
>
> > The other thing I wonder about this is when you executing
> > something like this are you going to the expense of
> > creating a record set when your using Oterro/RBase - ODBC.
>
> I don't know. I don't use record sets. I use arrays.
> Arrays are very fast, flexible and very easy to work
> with.
>
> > I am thinking more in an Oterro environment through VB...
> > I know when you execute just a single Executable command
> > against through an ADO object your are doing this at the
> > expense of a creating a record set just for a quick
> > simple responce. I have used this method, but would like
> > to find better ways.
>
> You don't need a record set to pull back a single
> value (nor would you use an array) and it seems to
> me that it would be rather inefficient to use one for
> this purpose.
>
> Scott
> ====
> Scott J. Salisbury
> Matrix Data Systems / The R:Street Journal
> 5114 Point Fosdick Drive NW, Suite E-272
> Gig Harbor, WA 98335-1733
>
> E-Mail Address: [EMAIL PROTECTED]
> Temporary URL: www.seanet.com/~sjs (downloads available)
> New Web Address: www.rStreetJournal.Com
> Direct Line: 206-423-7679
> Toll Free: 888-386-5040
> Seattle: 206-448-7975
> Fax: 305-425-0491
>
