Hey Scott, Bill, Manuel..
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 ???
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 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.
Jim Limburg
Scott Salisbury wrote:
>
> Manuel,
>
> This was my point exactly. Additionally, you can use
> SQLExecDirect to set environment variables (very
> cool if you've embedded variables in any of your
> views). You can also retrieve those environment
> variables in the same way.
>
> SELECT .x FROM Sys_Tables WHERE LIMIT = 1
>
> Scott
> ====
> Manuel de Aguiar wrote:
>
> > I think you guys missed the point. The objective of Scott post is to obtain
> > information from an RBase engine through ODBC. If on the Tango editor you
> > pick SQL Query [Ctrl]Q and was to enter:
> > SHOW VERSION or (CVAL('VERSION')), ODBC returns an error message:
> > "This command is currently unsupported (1120)S1000"
> >
> > HOWEVER, if you type:
> > SELECT (CVAL('Version')) FROM anyloggedtable WHERE LIMIT= 1
> >
> > ODBC returns from RBase:
> >
> > Oterro 2000 v6.5++ Windows (32-bit), U.S. Version, Build:
> > 1.842xRT03
> >
> > This is a great trick to get RBase function *** not a part of ODBC or SQL
> > *** from RBase!
> >
> > I LIKE IT!
> > Thanks,
> > Manuel
> >
> > Bill Downall wrote:
> >
> > > Jim,
> > >
> > > Take your anti-anxiety medications, and don't worry. Scott is either
> > > making extra work for himself, or being lazy, depending on your point of
> > > view.
> > >
> > > You could also do this:
> > >
> > > SET V vVersion = (CVAL('VERSION'))
> > > SHO V vVersion
> > >
> > > Scott is using a technique that lets him do it with a single command,
> > > by selecting the "expression" -- and no columns -- from a table that he
> > > knows you have in your database. By the time he adds the WHERE
> > > clause, so that you only see the answer once, it's probably as much
> > > work as the two commands above.
> > >
> > > Many developers create a one row, one column table named Dummy to
> > > enable tricks like Scott's.
> > >
> > > Bill
> > >
> > > On Fri, 21 Sep 2001 16:28:05 -0400, Jim Limburg wrote:
> > >
> > > >Where on earth did you learn a command like this...?
> > > >Where is it in the docs?
> > > >
> > > >Someone's holding out on me...
> > > >I,I,I just don't know what to think about how
> > > >deprived I feel right now...
> > > >
> > > >OK, OK,,, I'm settled down now...
> > > >Whew... I still am interested in learning more
> > > >about this...
>
> ====
> 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
