Tim,

<<If it cannot be done by SQL.  Then how to create a float field with a certain numbers of decimals?  I tried to use DECIMAL (20,2) but I still
can
edit this field with more than two decimals.>>

Sorry, never tried DECIMAL, but FLOAT(20,2) does not work.

Tim,

> Well, first of all, I wouldn't suggest using Float fields for currency
> storage, period.  I would use a DECIMAL or NUMERIC (same thing) column type
> instead.  

That's interesting. Why does the migrator then change currency fields to
float fields?

Regards Uli

Tim,

> Well, first of all, I wouldn't suggest using Float fields for currency
> storage, period.  I would use a DECIMAL or NUMERIC (same thing) column type
> instead.  

What about compatibility?

Abdulaziz Jasser <jasser@cyberia.net.sa> wrote:

Tim,

<<If it cannot be done by SQL.  Then how to create a float field with a certain numbers of decimals?  I tried to use DECIMAL (20,2) but I still
can
edit this field with more than two decimals.>>

<<Sorry, never tried DECIMAL, but FLOAT(20,2) does not work.>>

It does not work.  I will have to do all alot of work becuase of the SQL.  So much to pay.

Abdulaziz

>What about compatibility?

You can only go so far with compatibility -ask M$

Roy Lambert [Team Elevate]

Abdulaziz

>It does not work. I will have to do all alot of work becuase of the SQL. So much to pay.

In what way does it not work?

Roy Lambert [Team Elevate]

Uli,

<< That's interesting. Why does the migrator then change currency fields to
float fields? >>

It doesn't - Delphi does.  All of this is Delphi, and has very little to do
with EDB.

--
Tim Young
Elevate Software
www.elevatesoft.com

Abdulaziz,

<< Sorry, never tried DECIMAL, but FLOAT(20,2) does not work. >>

You cannot create a FLOAT field with a certain number of decimals in either
DBISAM or ElevateDB.  Delphi controlled the number of decimal places via the
edit and display masks that it used, but DBISAM did not control this.  This
is one of the major reasons why you should be using DECIMAL or NUMERIC (BCD
in DBISAM) instead.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

> It doesn't - Delphi does.  All of this is Delphi, and has very little to do
> with EDB.

Misunderstanding - I mean: an old currency-field in DBISAM is converted
into a float-field when using the DBISAM-EDB-converter.

Furthermore there could be serious problems truncating values instead of
rounding them, if you replace a float (currency)-field by a decimal field.

Uli

Tim,
Roy,


<<You cannot create a FLOAT field with a certain number of decimals in either
DBISAM or ElevateDB.  Delphi controlled the number of decimal places via the
edit and display masks that it used, but DBISAM did not control this.  This
is one of the major reasons why you should be using DECIMAL or NUMERIC (BCD
in DBISAM) instead.>>

Let say I decided to use DECIMAL type as the currency field.  This field is used in the "OnCalcFields" event of the TEDBtable component that
used to open memory table.  I get an error saying the field does not exist.  I usually define a field with the same name as an aggregate field to
come over this error.  The question: what type should I use when defining this field as aggregate field to make it compatible with DECIMAL
type?