You can do this in SQL Server with a table trigger, but unless I'm well
out of date, Access doesn't support triggers.
The only way to enforce this would be if you can be completely sure
that the table can only be updated through a particular form - then in
the Before_Update event of the form you can set CustCode according to
AutoFwrd.
There's a question why you'd want to do this at all, though - having
fields that depend on other fields is almost always a bad idea, as
there's a risk that one field will get updated to become inconsistent
with the other. This can make things very confusing, especially in
large datasets.
You could calculate CustCode on the fly anytime by doing a
SELECT AutoFwrd,Iif(AutoFwrd=True,"DP",[something else for False]) AS
CustCode FROM tblLeads.
going on the hunch that "if users can find a way to mess up the data,
they will", I'd advise against having fields derived from other fields
in a table.
cheers
Seb