Tim

>Actually, the fastest is to use the word size of the processor, i.e. 32-bit
>Integer for 32-bit processors, and a 64-bit Int64 for 64-bit processors.

In that case can I please have tables who's columns morph according to whatever processor they happen to be running on, oh yes and if its c/s I want them to morph for the server and all the clients simultaneously!

Roy Lambert

Roy Lambert <roy.lambert@skynet.co.uk> wrote in
news:F6E71EB1-CB79-42CB-B54C-A80E97F64AC4@news.elevatesoft.com:

> Tim
>
>>Actually, the fastest is to use the word size of the processor, i.e.
>>32-bit Integer for 32-bit processors, and a 64-bit Int64 for 64-bit
>>processors.
>
> In that case can I please have tables who's columns morph according to
> whatever processor they happen to be running on, oh yes and if its c/s
> I want them to morph for the server and all the clients
> simultaneously!
>

Roy, I seem to recall that when Delphi went from version 1 (16-bit) to
version 2(32-bit) Integer went the same route.

So perhaps you could just use Integer and hope for the best

--
Chris
(XP-Pro + Delphi 7 Architect + DBISAM 4.25 build 4 + EDB 1.02 build 1)

Chris


>So perhaps you could just use Integer and hope for the best

Strangely enough ........

Roy,

<< In that case can I please have tables who's columns morph according to
whatever processor they happen to be running on, oh yes and if its c/s I
want them to morph for the server and all the clients simultaneously! >>

Well, my guess would be that 99% of the processors out there where your
application will be running are still 32-bit processors.  Put it this way -
EDB uses 32-bit integers internally whereever possible.

--
Tim Young
Elevate Software
www.elevatesoft.com