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??
If I edit a table directly in SQL Server and want to add an index or key, there are four options:
1. Primary Key - straight forward, no issues.
2. Unique Index - straight forward, no issues.
3. Non-Unique Index - straight forward, no issues.
4. Unique Key - this is the option that I can't figure out how to do. This is a secondary key that must be unique - enforced through a constraint. In addition, an index is created.
Tables -> Indexes -> Index Properties
Thanks,
Flavelle