>Hi Nadya,
>
>I would rethink using APPEND BLANK in your framework if I were you. What I do is a method that accepts the table and primary key value and primary key field. Then I use INSERT INTO ... () VALUEs (). APPEND BLANK is going to cause problems, especially if the app comes down and a blank record gets left in the base table. Thereafter, the app will break the next time an APPEND BLANK is issued, as you are finding out.

I agree, but it would be tough task to convince to change code in our framework :(. Even one simple property in grid nCurRec to add I had to have a long discussion to convince to add it. :(

>
>
>>>Yup. Generate the value and use INSERT INTO instead of APPEND BLANK. Create the PK value before the INSERT.
>>
>>Append blank is in our FrameWork :( I don't want to write special code for this particular form, though it seems like I must.
>>
>>>
>>>>Hi everybody,
>>>>
>>>>I have a table, there field Code (Character 6) is made PK. This table contains one blank record (this is by design). Now, each time I'm issuing append blank, I get an Error "Uniqueness of indexes is violated". I'm thinking about adding a default value for this field, but I don't want to use NextID table approach, because this database doen't have a NextID table and I don't want to change it.
>>>>Therefore I'm seeking for the idea of a function, which will generate Unique ID automatically (Char 6).
>>>>
>>>>Or may be you have other ideas? Simple way, which was suggested by my manager, just make this index to be regular and deal this checking on the form level. I disagree, because our data is not secure enough, so if somebody will edit this table directly, there is a chance for adding duplicates.
>>>>
>>>>What do you think? I know, it's not recommended to use character PK (meangful), but this table was designed long time ago and I don't want to change it.
>>>>
>>>>Thanks in advance.