Borland®
Shop
Products Downloads Services Support Partners News & Events Company Community

Updates & Patches
AppCenter
AppServer
Borland C++
BDE
Borland Enterprise Server
C++Builder
CodeWright
Delphi
InterBase
Janeva
JBuilder
JDataStore
Kylix
Optimizeit
Pascal
Security Service
VisiBroker

Community Site
AppServer
C++
CORBA
Delphi
InterBase
Java
Linux
Search
Advanced Search

 BDE/SQL DEVSUPPORT

Borland Database Engine/SQL Links 5.01
Enhancements and Fixes

GENERAL SECTION


Areas of concentration under: general


Area: general

Reference Number: 9
Status: Fixed
Sub Area: Delayed/Deferred Update
Date Reported: 03/12/97
Severity: Critical
Type: Basic Functionality Failure

Problem:

The OnUpdateRecord event may be called multiple 
times after a exception occurs during a call to 
ApplyUpdates.

Area: general

Reference Number: 17
Status: Fixed
Sub Area: Upsizing Tool
Date Reported: 04/02/97
Severity: Critical
Type: Basic Functionality Failure

Problem:

If the password for a paradox table has accented 
characters, the password validation fails.

Area: general

Reference Number: 28
Status: Fixed
Sub Area: Table Open, Properties
Date Reported: 05/13/97
Severity: Critical
Type: Basic Functionality Failure

Problem:

Field sizes on pseudo-blobs and blobs now return a 
different iLen than with earlier version of the BDE.  
This in its self is not a problem but Delphi, in some 
cases, holds field and blob sizes in the EXE causing 
an exception "field < field_name > is not of 
expected type".  In effect, every Delphi2 
application that used the BDE3.x to create the field 
information, now cannot run with BDE4.0

Area: general

Reference Number: 13
Status: Fixed
Sub Area: Sessions
Date Reported: 03/19/97
Severity: Serious
Type: Crash

Problem:

Delphi32 AV's when changing the 
Session.NetfileDir property after the table was also 
used in a different session.

Area: general

Reference Number: 72
Status: Fixed
Sub Area: Local SQL
Date Reported: 06/23/97
Severity: Serious
Type: Crash

Problem:

select * from "c:\order.db", "c:\test\order.db"

When the field names in 2 tables are different, it 
crashes.

Area: general

Reference Number: 4
Status: Fixed
Sub Area: Delayed/Deferred Update
Date Reported: 02/26/97
Severity: Serious
Type: Basic Functionality Failure

Problem:

After inserting a record and applyUpdates if a 
record is deleted the following record will appear to 
be deleted as well.

Area: general

Reference Number: 62
Status: Fixed
Sub Area: Delayed/Deferred Update
Date Reported: 06/11/97
Severity: Serious
Type: Basic Functionality Failure

Problem:

Updating a Key Violation causes an "At end of 
Table error."

Area: general

Reference Number: 71
Status: Fixed
Sub Area: Delayed/Deferred Update
Date Reported: 06/20/97
Severity: Serious
Type: Minor Functionality Failure

Problem:

With cached updates turned on, cannot read from 
a Paradox blob field (using DbiOpenBlob or 
DbiGetField) if it's invariant field position was 
changed since the table was originally created.  
Gives a 'Field is not a Blob' error.

Area: general

Reference Number: 74
Status: Fixed
Sub Area: Local SQL
Date Reported: 06/26/97
Severity: Serious
Type: Minor Functionality Failure

Problem:

When a subQuery has an invalid field name, you 
got an error "BDE error $0001". Should get an error 
msg DBIERR_INVALIDFIELDNAME.

Sometimes you got another error msg "File or 
directory does not exist. File: 
c:\junk\pdoxusrs.lck......."

Area: general

Reference Number: 20
Status: Fixed
Sub Area: Local SQL
Date Reported: 04/11/97
Severity: Commonly Encountered
Type: Crash

Problem:

Problem  using live SQL cursor when   trying to 
switch indexes and the WHERE clause includes a 
field of an existent index. 

Apparently indices get lost. curProps.Indexes 
returned by DbiGetCursorProps is equal 0. 
.
SELECT * FROM TABLE WHERE STATE='CA'

where "state" has a primary index.

Under 3.5 Access Violation

Area: general

Reference Number: 24
Status: Fixed
Sub Area: Delayed/Deferred Update
Date Reported: 05/05/97
Severity: Commonly Encountered
Type: Basic Functionality Failure

Problem:

Using delayed updates on any table which has a 
record size greater than about 4090 creates errors 
such as "capability not supported" (InterBase) and 
"invalid field name" (Paradox)

Area: general

Reference Number: 42
Status: Fixed
Sub Area: Delayed/Deferred Update
Date Reported: 05/22/97
Severity: Commonly Encountered
Type: Basic Functionality Failure

Problem:

With a certain record buffer size, a call to 
DbiBeginDelayedUpdates retruns an error "Invalid 
field type. Field: Field12.".

Area: general

Reference Number: 61
Status: Fixed
Sub Area: Delayed/Deferred Update
Date Reported: 06/11/97
Severity: Commonly Encountered
Type: Basic Functionality Failure

Problem:

Using a master / detail relationship with cached 
updates, occasionally error 'at end of table' 
appears.  If two records are added to the master 
table and then one record is added to the second 
master record (leaving no detail records to the first 
master record), then applying updates, 'at end of 
table' occurs on the detail apply.

Area: general

Reference Number: 64
Status: Fixed
Sub Area: Sessions
Date Reported: 06/12/97
Severity: Infrequently Encountered
Type: Basic Functionality Failure

Problem:

Calling DbiStartSession then DbiCloseSession in a 
loop will eventually lead to an error 'Insufficient 
Memory for this Operation'.  This can be a big 
problem especially for ISAPI and NSAPI 
applications that start multiple threads and keep the 
BDE loaded in memory.



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.

 
Site Map Search Contact