Kbase P11605: Attempt to create duplicate keys results in blank records when using ADM1 and Dataservers
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/08/2005 |
|
Status: Verified
FACT(s) (Environment):
DataServers
Progress 9.1x
SYMPTOM(s):
Attempt to create duplicate keys results in blank records
<record> already exists with this unique index value. (2471)
After the 2471 error a blank row is left in the SmartDataBrowse or SmartViewer
A Blank record is created in the table
CAUSE:
This is expected behavior.
In v8 the attribute adm-create-on-add had a default value of no.
In v9 this value is set to ? by default and also calls RUN use-create-on-add( ? ) in tableio.i.
The default for behavior Progress DBs is no - the Create happens when the record is Saved.
The default for non-Progress DBs is yes, because there is no other way to display initial values properly.
FIX:
To stop blank rows from being created immediately,go to the Instance Attributes of the SmartDataBrowse or SmartViewer, select no for the "Create new record immediately on 'Add'" property. But remember that this will cause new records in a viewer to do not initiate with their initial values.