Thanks,
Flavelle
If you are trying to create a column that is unique in addition to the primary key it should work as described in the DDT help. It is simply a constraint; hence, SQL will throw an exception and you would have to programmatically deal with it in code.
Typically we avoid duplicate records by creating a function within the BO and include the verification in the CheckRulesOnCurrentRow method.
The following code should help.
Steve
---------------------------------------------------------------
For example,
loCommand.CommandText =
Clear as mud??