🚀 go-pugleaf

 > Isn't Insert() supposed to insert an empty
 > record into the database?

Yes and No. It will try to insert a new record, but what you are 
encountering is a Primary Key field not being unique (is my guess). An 
example would be something like this:

If I wanted to have a database of people and I used their Social 
Security Number as a key, I wouldn't want any record to have a duplicate 
SSN#. So I would make this field my Primary Key. Now the Database knows 
that there will be no duplicates and if there is it will throw an 
exception. (Same goes if you are not assigning any value, the second no 
value might give you a error since it would be a duplicate)

I would suggest you looking at your Primary Key and seeing how it is 
being filled.

David


Jens Weiermann wrote:

> Hi! I'm trying to import some data from ascii files into a SQL server
> database. This is the code I'm using:
> 
>                ADOTable1->Insert();
>                ADOTable1->FieldByName("ChipNr")->AsString = ChipNr;
>                ADOTable1->FieldByName("Direction")->AsString = "I";
>                ADOTable1->FieldByName("Date")->AsDateTime =
> StrToDateTime(DatumZeit);
>                ADOTable1->Post();
> 
> However, the ADOTable->Insert() throws an exception, stating that the
> primary key would be violated. Isn't Insert() supposed to insert an empty
> record into the database? I expected the PK violation when issueing the
> Post() statement, not when Insert()ing ...
> Any clues?
> 
> Thanks,
> Jens
>