New Incident Reports for 3.21

New Incident Reports for 3.21

The following is a list of the new incidents reported for version 3.21. Click on the incident # in order to view the details of the incident report.

Serious Problems

Build

#

Title

Workarounds

1	1293	CopyTable Method of TDBISAMTable Component Resetting Last AutoInc Value if Table is Empty	Yes
1	1294	Wrong Results with Parameters in SQL WHERE Clause	Yes
1	1297	EXTRACT WEEK Function Returns Incorrect ISO Week Number	No
1	1302	SQL DELETE Statement with Join Condition Not Working Correctly When No Indexes Exist for Joins	No
1	1316	In-Memory Tables Lose Their Proper Location After a C/S Re-Connect	No
1	1318	Using More Than One % Wildcard Character at the End of a LIKE Constant Returns Incorrect Results	Yes
1	1321	DBSYS Reverse Engineering to SQL Causes Script Error When Table Description Contains Quotes	Yes
1	1322	Using an Invalid SQL LAST AUTOINC Clause in ALTER TABLE Results in 0 Value in Table	Yes
1	1323	Potential AV Could Occur in Engine Change Detection During a Locate Method Call	No
1	1324	Possible AV During Batch SQL INSERTs Within a Transaction	No
1	1325	COALESCE SQL and Filter Function Leaking Memory	No
1	1326	Restructuring a Table by Changing Index Information Only and then Cancelling Causes Index Corruption	Yes
1	1327	Any Severe Error (AV, etc.) in C/S Session Causes Problems when Server Tries to Remove Dead Session	No
1	1328	Trying to Create a Table in an Invalid Directory Causes Subsequent AVs	No
1	1329	ODBC Driver Can Cause Too Many Blobs Open Error (#9494) When Used with Access XP Form	No
1	1343	Copy and Paste is Not Working for the SQL Query Window in DBSYS Utility	Yes
1	1354	Invalid Date/Time Values in String Fields Converted To Date/Time Fields Causes Invalid Dates	Yes

Minor Problems

Build

#

Title

Workarounds

None

More Support Options

Search Incident Reports

Frequently Asked Questions

Technical Bulletins

Technical Articles

Product Manuals