I make a test  comparativ with  Bde 2.51 ( 16bit Delphi 1 ) and Bde 5.01 (
32bit Delphi 4 ), and the result is stupid. Why this result ?

Le test is 3 query with paradox tables.
The machine is  reboot and very clean.
The connection to the database is OK. ( Session.opendatabase ( DatabaseName ) )

The time test is the actived of the 3 querys

in second time the Tquerys are false avtived.

16bit BDE functionality is no longer being actively supported
by dang near anyone these days, so even if the 16bit
architecture was 10 times faster it doesn't really matter.

One thing to remember is that the 16bit BDE supports far
less SQL features than the 32bit version.

GW.

Let's say you bring a new 'fast, full 32-bit version' of your app to
your client. And that turns out to be 40..50% slower than the 16-bit
oldie. It usually matters, if the previous 3 second response time
grew to 6 seconds.

It can mean that you even have to postpone all your 32-bit product
versions, and instead start to consider and implement some totally
different database solutions.
It usually means extra burning of somone's money. You are lucky if
the client agrees that he/she of course is the object to handle
these bills.

The client may think that the extra functionality that you
*may* be able to provide with the 32bit application offsets
the speed/performance penalty incurred by the change
from 16 to 32 bits.

BTW, these figures were quoted going from 16 to 32 bit
BDE.  The BDE, for me, is simply not good enough for
any client.  Ditch the BDE and use something altoghether
better, like DBISAM, GMDAO/ADO, ADOExpress,
InterbaseExpress or IBObjects.

I don't notice any speed difference between 16 bit DBISAM
and 32 bit DBISAM.  They're both reeeeeeeeeeeeally fast.

Graham Wood - gdW fleetWare.

I kind of like the simple, clear idea that if you change either your
hardware or software from 8-bit to 16-bit, again from 16-bit to
32-bit, and next year up to 64-bit, on every step you get faster,
or at least not slower products as you had earlier.