You should specify the column names to prevent this from happening.

Such as ...

INSERT INTO rcensioni (col1,col2,etc) VALUES ('value','value','etc...')

Just make sure you don't specify the column that is autonumbering.


>Always struggling on my php-odbc-MS access project, I managed to successfully
>add a record to a table.
>Now, no matter what I write in the first field (random numbers, AUTO,
>I get this:
>Insert Into recensioni VALUES (300, 'riee', 'reworew', 'wer', 2001,'IT', 2.5,
>'dond to it, 'rew', 'uno',1, 'Caro', 3, 'stuff',
>20011205201040, 'writeurl, 1, '5/12/2001 20.10.40', '1', '1','enter keyword')
>Warning: SQL error: [Microsoft][ODBC Microsoft Access Driver] The changes you
>requested to the table were not successful because they would create duplicate
>values in the index, primary key, or relationship. Change the data in the
>field or fields that contain duplicate data, remove the index, or redefine
>the index to permit
>duplicate entries and try again., SQL state 23000 in SQLExecDirect in
>C:\domini\mnet\inser_rec.php on line 109
>Error in odbc_exec( no cursor returned )
>How can I find out what I am duplicating? The first field is the unique key,
>but what should I send to Access to tell it just auto increment and go?
>If I put 0 or NULL it complains.
>Also, Andrew Hill siggested the use of odbc_tables and odbc_columns to get
>info about the structure of each column which I don't know in detail because 
>the DB was written by the guy who quit, not me....)
>What is the exact syntax of those instructions? I have tried to apply the
>manual, but without success on the second one.
>       TIA,
>               mweb
>PHP General Mailing List (
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>To contact the list administrators, e-mail: [EMAIL PROTECTED]

Jim Musil
Multimedia Programmer

PHP General Mailing List (
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to