Hello Tim,
  Using EDB Manager:
  1) Create a new database
  2) Migrate a DBISAM v4 table (with blob)
  3) Click - Alter a table
  4) Find a Blob field and change it's compression to "Max"
  5) Hit OK
  6) Alter table again

The compression will stay to "None" (was to none)

btw, it doesn't migrate compression settings from dbisam too.

--
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 (with blob)
  3) Click - Alter a table
  4) Find a Blob field and change it's compression to "Max"
  5) Hit OK
  6) Alter table again

The compression will stay to "None" (was to none)

btw, it doesn't migrate compression settings from dbisam too. >>

Fixed.

--
Tim Young
Elevate Software
www.elevatesoft.com

Michael,

I actually should have explained more about this.    This item:

<<  btw, it doesn't migrate compression settings from dbisam too. >>

is fixed.

This item:

  Using EDB Manager:
  1) Create a new database
  2) Migrate a DBISAM v4 table (with blob)
  3) Click - Alter a table
  4) Find a Blob field and change it's compression to "Max"
  5) Hit OK
  6) Alter table again

The compression will stay to "None" (was to none) >>

Is normal (at least for now).   After editing a column, you have to hit the
Edit button to save the changes for the column.  However, EDB currently only
allows you to modify these aspects of a column during an alter:

1) Default clause
2) Description
3) Position in the table

This will most likely be opened up further for the final release, but the
SQL standard only dictates that you support the changing of the default
clause or identity column seed values (which EDB doesn't support currently).

--
Tim Young
Elevate Software
www.elevatesoft.com