At initialization time, you can specify the initial settings for the primary
key in the UI.
You cannot use this attribute to determine the primary key, possibly created
by the wizard, after it finished. The reason is that during the wizard run, the
user can define an arbitrarily complex primary key, e.g. including multiple columns,
which cannot be represented in this simple attribute anymore.
This attribute is ignored if Operation is
CopyTableOperation::AppendData.
Changing this attribute while the dialog is running is not supported, the
result of such an attempt is undefined.