RE: Changing database to SQL from DDS

I can easily see how converting from DDS defined files to SQL would 
enhance performance.

Many CASE tools, (like AS/SET), have built in code to check referential 
integrity.  For example, before I add a record to the order line file I 
must make sure that the order header exists, part number exists, etc. Now, 
if you have all of your constraints defined to the file, and you 
adequately check the error upon a write/update, then all of this garbage 
is done for you by the OS.  And RI handled by the OS is going to blow the 
doors off of RPG.

But the catch is in the conversion.  You would have to add the RI to the 
SQL.  A simple tool that converts DDS to SQL isn't going to do that.

Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin