Hi Mike,

Due to the fact that the DBC is not terribly robust, structurally, I avoid any DBC code like the plague. Call it a personal preference :-)

With the upcoming VFP.NET, I think we're gonna see DBC events which may allow you to create Custom classes to intercept things at whatever level you like.

Meanwhile, I would advise against DBC-level code.

>Way back in the days of VFP 3.0, record level vaidation, rules and triggers got a bad rep because they didn't work too well. When our app was finally released in VFP 5.0, we put code in the base class of our data entry forms to write an integer value into new/updated/deleted records.
>
>I've still heard some bad things about triggers, but since you can't modify the record that set off the trigger, they're not what I'm looking for anyway.
>
>A record level validation that wrote the integer and always returns .t. seems to work in testing. Anyone have real-world experience with this type of thing that would like to pass it on?
>
>Thanks in advance,
>Mike