erichf wrote: It looks like that fix addresses the problem. I tripped over the fact that the dblookup field has to come after the other fields being evaluated but once I got that correct, it works fine.
Is there a way to generate more meaningful error messages for the user other than the standard `field name: "Invalid Code"` message which is hard coded in dblookupfield.php? Can this be extracted out to a language file so it's not a core hack if we change that message?
Thanks
Erich
Yeah - I need to make these language ready - on my 2do list.