RE: While we're on the subject, a more complicated SQL question.

Joe,

in a previous life (gosh it seems a long time ago) I would have used
STRSQL, but i'm contracting at a place that doesn't see the benefit of SQL,
and i'm in no position to tell them how to do thier jobs.

i use some QMQRY when I want to save something, but mostly I use EXCSQL
(somebody's freeware Brad Stone maybe? sorry whoever, I don't remember).
It doesn't archive it, but it's in my cmd history so if I want to save it
for later, i'll cust and paste it somewhere.

it's been a while, but does STRSQL allow you to delete bad commands? or
delete commands you don't want to 'remember' or do you have to edit the
session in SEU or some such to clean it up?

I ask, because sometimes, i'll type in a command 4 or 5 times before I get
the syntax right - especially because it uses a command interface, excsql
wraps your statements with quotes and doubles any that you use in your
statement, so it increases my chances of missing a quote here or there.

oh, how I wish I had the sql product......

have a great weekend everyone,

rick

---original message-------------------
> From: Richard B Baird
>
> i'd done it before a long time ago, but forgot how.  hopefully i'll
> remember next time, and at least now it'll be in the archives.

I'm hoping you used STRSQL? to do this. If so, you could have saved the
session in a text file.  In fact, you probably still have the instructions
in the "magical STRSQL buffer", and if you did a STRSQL again, you'd see
those old instructions.

If that's the case, if'n I wuz you, I'd immediately do a STRSQL, then hit
F3
and on the "Exit Interactive SQL" session, select option 4 to "Save session
in source file".  You have options to create a brand new file and/or
member,
and then save the session.  Do this every time you do something new and
cool
or useful.

You'll eventually end up with a whole slew of snippets in there that you
can
then cut and paste when you need something.  They're also nice as a basis
for embedded SQL statements.

(See folks?  I really DO use SQL!  Honest!)

Joe