ID Number: Q69282
1.10 1.10a
OS/2
buglist1.10 fixlist1.10a
Summary:
Changes Incorporated in the 10/03/90 Build of SQL Server (1.10a)
----------------------------------------------------------------
TITLE
ISQL confuses GOTO and GO if begun in column 1.
DESCRIPTION
If a GOTO command is put in column 1 of an ISQL script, ISQL
treats it as a GO command.
TITLE
SAF crashes on cumulative errors.
DESCRIPTION
When making iterative changes in the query window after errors, SAF
locks up MS-DOS or causes a GP fault in OS/2.
TITLE
Delay in results from SAF when running on the server machine.
DESCRIPTION
Running the original 1.1 released version of SAF on the same
machine as your SQL Server causes a delay in the displaying of
returned results. If you switch screen groups and go back into
SAF again, the results will be displayed normally.
TITLE
Errors in dumping from SAF.
DESCRIPTION
If a user tries to dump a database twice in a row from SAF, the
message "Error 53 from DOSOPEN trying to open" is displayed the
second time the dump is attempted. In addition, this same error
occurs when trying to dump a database from SAF and SQL Server is
in single-user mode.
Note: When the same database is now dumped twice in a row in
single-user mode, the error still occurs.
TITLE
Embedded GOs with SQL syntax error(s) cause SAF to GP fault.
DESCRIPTION
In SAF, if a GO command is embedded in a series of SQL
statements, and any one of those statements contains a SQL syntax
error, execution of these statements causes problems. SAF will
return a normal syntax error; however, the next time CTRL+E is
pressed, SAF will GP fault in OS/2, or hang the machine in
MS-DOS.
TITLE
Cannot print from SAF in stand-alone mode.
DESCRIPTION
When SQL Server is installed stand-alone, the user cannot print
from SAF. In addition, no printer list is displayed when the
Select Printer option is chosen from the File menu in SAF.
TITLE
TCOUNT(DISTINCT...) causes the server to GP fault.
DESCRIPTION
If a query with the COUNT(DISTINCT <column>) function is
executed with a WHERE clause of "WHERE 1=2", the server GP faults.
TITLE
#defines missing cause unpredictable behavior.
DESCRIPTION
If a program does not include the #define DBMSDOS or #define
DBMSOS2, it may compile with no errors; however, it may lock up a
MS-DOS machine, cause a GP fault in OS/2, or even bring down the
server.
TITLE
bcp_exec() errors.
DESCRIPTION
Calls to the bcp_exec() function fail under certain environments.
TITLE
bcp_init() fails under Windows version 2.11.
DESCRIPTION
If a program is linked with WDBLIB.LIB, calls to the bcp_init()
function fail under Windows version 2.11.
TITLE
dbbind() causes an application to crash when using global memory.
DESCRIPTION
When trying to bind variables of type NTBSTRINGBIND that have
been allocated in global memory using the GlobalAlloc() function
in Windows version 3.0, or the DosAllocSeg() function in OS/2,
the dbbind() function fails.
TITLE
dbexit() does not work with multiple instances of a program.
DESCRIPTION
When using the Windows version 3.0 DB-LIBRARY (db-lib) and two
instances of SQLTEST3 are run, and one is then closed, the
dbsqlexec() function fails on the other.
Note: Under Windows version 3.0, instead of using the dbexit()
function, the dbwinexit() function should be used instead. However,
the sample code still uses the dbexit() function.
TITLE
dbwinexit() locks up the machine.
DESCRIPTION
If two instances of the same Windows version 3.0 program
are run that execute the dbwinexit() function on completion,
and the second instance is exited, the machine locks up.
TITLE
dbtxtsnewval() fails in Windows version 3.0.
DESCRIPTION
If the dbtxtsnewval() function is executed in Windows
version 3.0, an unrecoverable application error (UAE) occurs.
TITLE
dbclrbuf() problems.
DESCRIPTION
If the dbclrbuf() function is called with the n > DBBUFFER
option, no rows are retrievable from the buffer. The
documentation states that the latest row should be available.
TITLE
Calling dbnextrow() after dbgetrow() works incorrectly.
DESCRIPTION
If the dbnextrow() function is called after the dbgetrow()
function, the incorrect row is returned.
TITLE
Incorrect results returned for dbcount().
DESCRIPTION
The dbcount() function returns the value 0 when executing a
stored procedure, such as UPDATE or DELETE, that does not return
any rows.
TITLE
dbqual() does not accept keys that allow null.
DESCRIPTION
The dbqual() function returns an incorrect WHERE clause and
the error message of "Requested data-conversion does not exist,"
if the unique key contains a column that at create time was
specified to allow nulls.
TITLE
dbqual() produces overflow error on two-column index.
DESCRIPTION
If the dbqual() function is used in BROWSE mode to produce a
WHERE clause against a unique index that contains two keys, the
length of the second key will be incorrectly calculated,
resulting in an overflow error and the error message of
"Data-conversion resulted in overflow."
TITLE
bcp_exec() causes GP fault while reading unformatted datafiles.
DESCRIPTION
If the application does not use the bcp_columns() and the
bcp_colfmt() functions to define the datafile, a GP fault will
occur when reading in data using the bcp_exec() function.
TITLE
Using BINDCHAR to bind to a CHAR(1) column in db-lib.
DESCRIPTION
Using the dbbind() function as follows
DBCHAR one_char;
...
dbbind (dbproc, column, CHARBIND, (DBINT) 1,
(BYTE *)&one_char);
does not work. An easy workaround that can be used is to change
(DBINT) 1 to (DBINT) 0.
.
TITLE
dbsetopt() buffers not being deallocated.
DESCRIPTION
The following problems with data structures not being
deallocated have been found:
- If the dbaltbind() function is used, the data structures
allocated for the binding are not deallocated.
- If a COMPUTE clause is used in a SELECT statement, some data
structures are not being freed.
- Use of the BY option in the COMPUTE clause, does not free a
certain data structure.
TITLE
Invalid textptr when text data is sent via bcp_sendrow().
DESCRIPTION
It is not possible to obtain a valid text pointer using the
txtptr() function if text data is inserted into a table using
the DB-LIBRARY BCP routines.
Additional reference words: 1.10 1.10a GP-fault dblib