Dec 262017
Shareware SQL Database, Version 3.1. Excellent intro to the SQL language. | |||
---|---|---|---|
File Name | File Size | Zip Size | Zip Type |
INSTALL.BAT | 1178 | 489 | deflated |
INSTDOC.EXE | 72476 | 72425 | deflated |
INSTSSQL.EXE | 234377 | 233770 | deflated |
READ.ME | 2177 | 1153 | deflated |
Download File SSQL31A.ZIP Here
Contents of the READ.ME file
*****************************************
* FOR INSTALLATION DETAILS TYPE INSTALL *
*****************************************
*** QUICK START (DETAILS IN DOCUMENTATION)
SSQL
(TYPE A COMMAND, SUCH AS)
SELECT *
FROM BRANCH;
(NOW PROCESS THE COMMAND BY PRESSING)
F4
(The response will be in the text box on the right. To close it press Alt-F3)
A fast way to erase the current query
(assuming the cursor is at the end of the query)
Shift-PgUp
Del
*** Output limit under SQL
The output of the select command is brought into an editing window. There
is a 65,000 character limit to the editing window. Anything above that will
get a "memory error". Since the output is put in a file called QUERY.TXT, you
can idit it with any text editor/word processor that can handle large files.
If you use SSQLENG directly the limit to the output is about 320,000 characters.
However, the size of the input tables remains UNLIMITED.
Work-around for file-save bug
When you create a new file, there is a bug if you press ALT-F3 to close the
window AND answer YES to saving an untitled file. It will probably lock-up.
Instead of pressing ALT-F3 to cloze a NEW file you want to save, press
ALT-F, A (Save As) to save the file, then close it.
Possible bug with mouse in VGA mode
If the mouse only goes down 25 lines when you are in VGA mode, do the following:
ALT-F, D (to shell to DOS)
exit (to get back to the program)
That should clear it unless you have a very old mouse driver.
Time-consuming queries
If your query takes a relatively long time (over 1000 tests), the word WORKING,
followed by a dot '.' for every thousand tests, will appear to let you know
that the computer has not locked up, it is just taking a while to evaluate
the query.
****** IF YOU HAVE A PC XT COMPATIBLE AND/OR NO HARD DISK *****
You may find SSQL a bit slow since every time you process a command, it has
to start SSQLENG. You can use SSQLENG directly which will greatly speed
processing on slow machines. See page INTRO-4 for a brief description of
SSQLENG, page WORD-1 and SCRIPT-1 for some hints to make working with
SSQLENG easier.
* FOR INSTALLATION DETAILS TYPE INSTALL *
*****************************************
*** QUICK START (DETAILS IN DOCUMENTATION)
SSQL
(TYPE A COMMAND, SUCH AS)
SELECT *
FROM BRANCH;
(NOW PROCESS THE COMMAND BY PRESSING)
F4
(The response will be in the text box on the right. To close it press Alt-F3)
A fast way to erase the current query
(assuming the cursor is at the end of the query)
Shift-PgUp
Del
*** Output limit under SQL
The output of the select command is brought into an editing window. There
is a 65,000 character limit to the editing window. Anything above that will
get a "memory error". Since the output is put in a file called QUERY.TXT, you
can idit it with any text editor/word processor that can handle large files.
If you use SSQLENG directly the limit to the output is about 320,000 characters.
However, the size of the input tables remains UNLIMITED.
Work-around for file-save bug
When you create a new file, there is a bug if you press ALT-F3 to close the
window AND answer YES to saving an untitled file. It will probably lock-up.
Instead of pressing ALT-F3 to cloze a NEW file you want to save, press
ALT-F, A (Save As) to save the file, then close it.
Possible bug with mouse in VGA mode
If the mouse only goes down 25 lines when you are in VGA mode, do the following:
ALT-F, D (to shell to DOS)
exit (to get back to the program)
That should clear it unless you have a very old mouse driver.
Time-consuming queries
If your query takes a relatively long time (over 1000 tests), the word WORKING,
followed by a dot '.' for every thousand tests, will appear to let you know
that the computer has not locked up, it is just taking a while to evaluate
the query.
****** IF YOU HAVE A PC XT COMPATIBLE AND/OR NO HARD DISK *****
You may find SSQL a bit slow since every time you process a command, it has
to start SSQLENG. You can use SSQLENG directly which will greatly speed
processing on slow machines. See page INTRO-4 for a brief description of
SSQLENG, page WORD-1 and SCRIPT-1 for some hints to make working with
SSQLENG easier.
December 26, 2017
Add comments