|
























|
 |
BDE/SQL DEVSUPPORT
Borland Database Engine/SQL Links 5.01
Enhancements and Fixes
DBASE SECTION
Areas of concentration under: dbase
Area: dbase
Reference Number: 29
Status: Fixed
Sub Area: Local SQL
Date Reported: 05/13/97
Severity: Critical
Type: Basic Functionality Failure
Problem:
FoxPro driver :
UPPER(), LOWER(), SUBSTRING() and TRIM() do
not work in Local-SQL statements if the table is a
FoxPro table, and the driver level is set to 25.
Returns error : Invalid Parameter.
Area: dbase
Reference Number: 36
Status: Fixed
Sub Area: Local SQL
Date Reported: 05/16/97
Severity: Critical
Type: Basic Functionality Failure
Problem:
//FoxPro driver - table level 25//
"Higher table level is required" when executing the
attached sql file which contains functions like
MAX() , MIN(), AVG()
Area: dbase
Reference Number: 80
Status: Fixed
Sub Area: Error Message
Date Reported: 07/14/97
Severity: Critical
Type: Basic Functionality Failure
Problem:
Non-live SQL queries against the attached table -
when Driver Level is set to 25 and Default Driver
set to DBASE - produces the error "Invalid
parameter. File or directory does not exist. File: <
path name > _QSQL000.DBF Table does not
exist."
This does not occur if the query is live or if the
Driver Level is set to 5 or lower.
Area: dbase
Reference Number: 63
Status: Fixed
Sub Area: Data Access
Date Reported: 06/12/97
Severity: Serious
Type: Crash
Problem:
FoxPro Driver:
If the table contains > 8192 records, adding a
new record causes Delphi/DBD to crash in
IDDBA32.DLL.
The table must have an index.
Area: dbase
Reference Number: 73
Status: Fixed
Sub Area: Data Access
Date Reported: 06/25/97
Severity: Serious
Type: Crash
Problem:
Cannot insert record in Fox table due to record
locking conflicts, causes GP.
Area: dbase
Reference Number: 30
Status: Fixed
Sub Area: Local SQL
Date Reported: 05/14/97
Severity: Serious
Type: Basic Functionality Failure
Problem:
FoxPro Driver :
The EXTRACT Date function does not work in
Local-SQL statements.
Area: dbase
Reference Number: 37
Status: Fixed
Sub Area: Local SQL
Date Reported: 05/19/97
Severity: Serious
Type: Basic Functionality Failure
Problem:
//Foxpro -table level 25//
Empty answer table is returned when executing the
below sql stmt which try to match a criteria and the
table is indexed.
SELECT type from table
where type='business'
Area: dbase
Reference Number: 59
Status: Fixed
Sub Area: Index
Date Reported: 06/11/97
Severity: Serious
Type: Basic Functionality Failure
Problem:
FoxPro Driver :
FindKey and Locate methods go to the wrong
record when a range is in effect. For example, find
key of 'D' goes to 'H'.
Area: dbase
Reference Number: 81
Status: Fixed
Sub Area: Dataset
Date Reported: 07/15/97
Severity: Serious
Type: Basic Functionality Failure
Problem:
Locate using loPartialKey in a String field does not
work for all tables.
Area: dbase
Reference Number: 40
Status: Fixed
Sub Area: Index
Date Reported: 05/20/97
Severity: Commonly Encountered
Type: Crash
Problem:
Doing anything with the index for the attached Fox
Table (adding an index, deleting an index, modifying
values in the index) creates various errors, the most
serious being an access violation when you try to
add an index. Works fine with Fox 2.5.
Area: dbase
Reference Number: 45
Status: Fixed
Sub Area: Index
Date Reported: 05/23/97
Severity: Commonly Encountered
Type: Crash
Problem:
Creating greater than 50 index tags on a FoxTable
generates an AV.
Area: dbase
Reference Number: 46
Status: Fixed
Sub Area: Index
Date Reported: 05/23/97
Severity: Commonly Encountered
Type: Crash
Problem:
Opening Fox Table with 49 index in Database
Desktop or getting a table list in Database Explorer
where the database includes a fox index with 49
indexes causes DBExplorer to crash to OS with no
error.
Area: dbase
Reference Number: 33
Status: Fixed
Sub Area: Local SQL
Date Reported: 05/15/97
Severity: Commonly Encountered
Type: Basic Functionality Failure
Problem:
//FoxPro driver//
[47][8] "Higher table level required" message is
returned when executing a sql stmt like :
select count(field) from table
where table is a foxpro table(table level 25)
Area: dbase
Reference Number: 34
Status: Fixed
Sub Area: Local SQL
Date Reported: 05/15/97
Severity: Commonly Encountered
Type: Basic Functionality Failure
Problem:
//FoxPro//
[27][2] "Invalid parameter" message is returned
when executing the following sql syntax against
foxpro(table level 25)
select field +(1/2) from table
Apparently is not handling operations with no
integers
Area: dbase
Reference Number: 60
Status: Fixed
Sub Area: Local SQL
Date Reported: 06/11/97
Severity: Commonly Encountered
Type: Minor Functionality Failure
Problem:
Dropping an index that does not exist returns error
'Index does not exist. Table : DBASE'. It should
display the table name, not the table type.
Area: dbase
Reference Number: 35
Status: Fixed
Sub Area: Local SQL
Date Reported: 05/15/97
Severity: Infrequently Encountered
Type: Minor Functionality Failure
Problem:
//Foxpro//
[27][2]"invalid parameter" is returned when excuting
the following stmt which one of the projectors is a
very large number like:
select 99999999999999, f1 from table
NOTE: These listings are for informational use only. It is
not intended for use when calling Borland's Developer Support Department.
If you have any suggestions or complaints about these
'BDE Enhancements and Fixes' pages, please contact the
BDE Administrator. This e-mail address is not intended for support issues.
|
|