1) This statement:

update informa.ziffern i set Custom = (select custom from
datamed.ziffern d where i.ziffer = d.ziffer);

results in an AV in EDBManager 2.03 Build 18, while in Build 17 it
results in this error message:

ElevateDB Error #1004 The column Custom in the table Ziffern cannot be NULL

There is no NULL value in either table!

2) This statement works in Build 17 while it results in an AV in Build 18:

update ziffern set Custom = false where ziffer in (select ziffer from
datamed.ziffern where custom = false)

Access violation at address 0055AB1F in module 'edbmgr.exe'. Read of
address 00000008

Uli

Uli,

<< results in an AV in EDBManager 2.03 Build 18, while in Build 17 it
results in this error message:  >>

If you have the execution plan checked, then un-check it.  It's a bug in the
execution plan generation for UPDATE statements.

--
Tim Young
Elevate Software
www.elevatesoft.com