Roy,

I already know the right syntax.  It was just a typing mistake.  The real problem is that I cannot limit the decimals to one used when creating
this field when editing the money field through a dbgrid.  Plus, this DECIMAL field does not give any attention/respect to the currency settings
in Delphi.  In DBISAM3 it was like doing nothing.

Abdulaziz,

<<  What do you mean?  After migrating a DBISAM3 to EDB database all the
currency fields became FLOAT and they don't respect the currency settings
any more! >>

Currency fields in Delphi are just float fields with built-in currency
formatting.  Just set the Currency property of the TFloatFields to True, and
you'll be all set.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

<<Currency fields in Delphi are just float fields with built-in currency
formatting.  Just set the Currency property of the TFloatFields to True, and
you'll be all set.>>

I have a complete knowledge of that.  What about those currency variables in Delphi?   Can they be applied automatically by EDB like DBISAM
without reformatting the fields?

Tim,

> Just set the Currency property of the TFloatFields to True, and
> you'll be all set.

With EDB I used the DisplayFormat property to show currency values.
Didn't see the currency-property at all
Thanks for pointing that out

Regards Uli

Abdulaziz,

<< I have a complete knowledge of that.  What about those currency variables
in Delphi?   Can they be applied automatically by EDB like DBISAM without
reformatting the fields? >>

I'm not sure what you mean.  Variables are handled entirely by Delphi, not
by DBISAM or EDB.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

<<I'm not sure what you mean.  Variables are handled entirely by Delphi, not
by DBISAM or EDB.>>

In DBISAM when you define a field as Currency it automatically adjust the number of decimals, currency string, thousand separator…etc  to the
one predefined in Delphi.  Now it doesn't.  I have to reformat everything myself to make this field appears like a real currency field.  I hope
the point is clear now.

Abdulaziz,

<< In DBISAM when you define a field as Currency it automatically adjust the
number of decimals, currency string, thousand separator…etc  to the one
predefined in Delphi.  Now it doesn't.  I have to reformat everything myself
to make this field appears like a real currency field.  I hope the point is
clear now. >>

DBISAM didn't do that - Delphi did.  All DBISAM did was indicate that the
field was a Currency/Float field.  Since ElevateDB only uses the SQL
standard FLOAT or DOUBLE designation, it can't possibly know which columns
you want to be used for storing currency values.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

<<DBISAM didn't do that - Delphi did.  All DBISAM did was indicate that the
field was a Currency/Float field.  Since ElevateDB only uses the SQL
standard FLOAT or DOUBLE designation, it can't possibly know which columns
you want to be used for storing currency values.>>


Can this feature be added to the SQL to make Delphi do it job?  It would save us (the developers) a lot of coding.

Abdulaziz,

<< Can this feature be added to the SQL to make Delphi do it job?  It would
save us (the developers) a lot of coding. >>

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.  Secondly, no, I don't think that we'll be adding this to
ElevateDB.  It was a remnant of the BDE/Paradox compatibility and it doesn't
translate well to other client front-ends.  It's similar to the Graphic and
FmtMemo types in this respect.

--
Tim Young
Elevate Software
www.elevatesoft.com

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.