thank you for your reply Hellen, but I still don't understand some things.

>Defining a default value has exactly one purpose: in an INSERT

statement, it overrides the >standard behaviour and ensures that a
specific value is written into a field that is not specified

>in the

INSERT statement. It is not intended to replace an explicitly passed
NULL and it won't

>work if you try to use it that way.

Firebird reacts the same if I write

insert into table (field1, field2,field3,...)
values(value1,value2, value3,...)���

where for example value2 is null

or

insert into table (field1, field2,field3,...)

values(value1,null, value3,...)

or

insert into table (field1, field3,...)

values(value1, value3,...)

generating the "field <field> value is null" for the field with the default source, (field2 in the example).

I know that when I "insert" into the table or the updatable view w/o BI trigger using some client software (e.g. IBExpert, FlameRobbin etc) it is not clear what the software does behind the scenes, but in this the case when I don't get the error message and the default value works. In all other cases it does not.

TIA,
Yannis







___________________________________________________________
�������������� Yahoo!;
���������� �� ���������� �������� (spam); �� Yahoo! Mail
�������� ��� �������� ������ ��������� ���� ��� �����������
��������� http://login.yahoo.com/config/mail?.intl=gr


[Non-text portions of this message have been removed]