RE: AW: Can I create an ALWUPD/ALWDLT *No file with embeded SQL?

<snip>
- Source can be changed (we do not use any scripting language either)
and that is far to risky.
<snip>

But defining the file with SQL doesn't entirely prevent someone from
being able to alter the contents if they really are determined (also,
you can create a source file in QTEMP which will go away once you are
done). You can use CPYF to create a new file with the same name and
field attributes and use it to replace the file you created with SQL.
The new file would then be changeable. Can user programs write to the
audit logs? That would seem to be the best way to do this. Alternately,
you could create the file on your system, put it in a save file, and
restore it on the client's system.

Matt