Hello Tim,
  Using EDB Manager:
  1) Create a new database
  2) Migrate a DBISAM v4 table
  3) Click - Alter a table
  4) Click - OK

You'll get:
  You must provide a valid version number error dialog
(Changing the version from "1,00" to "1" will accept it)

--
Charalabos Michael - [Creation Power] - http://www.creationpower.com -
http://www.creationpower.gr

Michael,

<< Hello Tim,
  Using EDB Manager:
  1) Create a new database
  2) Migrate a DBISAM v4 table
  3) Click - Alter a table
  4) Click - OK

You'll get:
 You must provide a valid version number error dialog (Changing the version
from "1,00" to "1" will accept it) >>

Fixed.

--
Tim Young
Elevate Software
www.elevatesoft.com

Hello Tim,

> << Hello Tim, Using EDB Manager: 1) Create a new database 2) Migrate
> a DBISAM v4 table 3) Click - Alter a table 4) Click - OK
>
> You'll get: You must provide a valid version number error dialog
> (Changing the version from "1,00" to "1" will accept it) >>
>
> Fixed.

Not fixed in build 3. It pops an error "Invalid floating value".
This may something to do with locales ? (I'm using Greek locale)

--
Charalabos Michael - [Creation Power] - http://www.creationpower.com -
http://www.creationpower.gr

Michael,

<< Not fixed in build 3. It pops an error "Invalid floating value". This may
something to do with locales ? (I'm using Greek locale) >>

Are you entering the value with a comma or a period ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

I tryed both here (PTG locale), and both are generating an error message:
-With "." the message is "'1.14' is not a valid floatig point value"
-With "," the message is "You must provide a valid version number"
(It is version 1.14 because the test table was migrated from DBISAM and had
that value).

--
Fernando Dias
http://www.easygate.com.pt/components

Hello Tim,

> << Not fixed in build 3. It pops an error "Invalid floating value". This may
> something to do with locales ? (I'm using Greek locale) >>
>
> Are you entering the value with a comma or a period ?

period

--
Charalabos Michael - [Creation Power] - http://www.creationpower.com -
http://www.creationpower.gr

Michael,

<< period >>

I'll look into it.

--
Tim Young
Elevate Software
www.elevatesoft.com

Fernando,

<< I tryed both here (PTG locale), and both are generating an error message:
-With "." the message is "'1.14' is not a valid floatig point value"
-With "," the message is "You must provide a valid version number"
(It is version 1.14 because the test table was migrated from DBISAM and had
that value). >>

Is this with the latest build (4) ?  I've tried both ways here with the
decimal separator set to a comma, and it works fine.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

> Is this with the latest build (4) ?  I've tried both ways here with the

No. It was with build 3. I'll try again with 4.

--
Fernando Dias

Hello Tim,

> Is this with the latest build (4) ?  I've tried both ways here with the
> decimal separator set to a comma, and it works fine.

Build 4 does it too. It's a problem with the ThousandSeparator
on different locales.

Try to replace StrToCurr with StrToCurrEx like:

function StrToCurrEx(const AValue: String): Currency;
begin
  Result := StrToCurr(StringReplace(AValue, ThousandSeparator,
EmptyStr, [rfReplaceAll]));
end;

On tabledlg.pas:
  if (StrToCurr(VersionNumberEdit.Text) <> Version) then //Here's the
exception.

--
Charalabos Michael - [Creation Power] - http://www.creationpower.com -
http://www.creationpower.gr