I got it to work but now I can figure out why I can't insert another
row referring to chasepreuninger. It works the first time then it
just fails.

CREATE TABLE Accounts (Account_Name VARCHAR(100) PRIMARY KEY,
First_Name VARCHAR(50) NOT NULL, Last_Name VARCHAR(100) NOT NULL,
Email_Address VARCHAR(300) NOT NULL);
CREATE TABLE Notes (Note_ID INTEGER PRIMARY KEY, Note_Owner
VARCHAR(100) REFERENCES Accounts(Account_Name), Note_TITLE
VARCHAR(50) NOT NULL, Note_Description VARCHAR(500) NOT NULL,
Note_Keywords VARCHAR(300) NOT NULL, Note_Location VARCHAR(100) NOT
NULL UNIQUE);
DROP TABLE Notes;

INSERT INTO Accounts VALUES('chasepreuninger', 'Chase', 'Preuninger',
'chasepreuninger (AT) gmail (DOT) com');
SELECT * FROM Accounts;

INSERT INTO Notes VALUES(3, 'chasepreuninger', 'Bio Lab 7', 'Here is
the lab we did today!', 'bio, biology', '5645656.doc');
SELECT * FROM Notes;

Error code -1, SQL state 23505: The statement was aborted because it
would have caused a duplicate key value in a unique or primary key
constraint or unique index identified by 'SQL080516093435302' defined
on 'NOTES'.
Line 8, column 1

hi,
Chase Preuninger wrote:
this is the italian localized NG for SQL Server, and questions should be
posted in italian..

your table is defined with a primary key on the Account_Name column..
primary key implies a unique value and this is the reason you can not insert
a duplicate for that column's value..
try defining another primary key instead the actual one.. you could perhaps
use an artificial key, perhaps based on a numeric column with an
autogenerated value like the Identity property provides..
read further about artificial keys in
http://www.intelligententerprise.com...leID=201806814
regards
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz http://www.hotelsole.com
DbaMgr2k ver 0.21.1 - DbaMgr ver 0.65.1 and further SQL Tools
--------- remove DMO to reply

hi,
Chase Preuninger wrote:
this is the italian localized NG for SQL Server, and questions should be
posted in italian..

your table is defined with a primary key on the Account_Name column..
primary key implies a unique value and this is the reason you can not insert
a duplicate for that column's value..
try defining another primary key instead the actual one.. you could perhaps
use an artificial key, perhaps based on a numeric column with an
autogenerated value like the Identity property provides..
read further about artificial keys in
http://www.intelligententerprise.com...leID=201806814
regards
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz http://www.hotelsole.com
DbaMgr2k ver 0.21.1 - DbaMgr ver 0.65.1 and further SQL Tools
--------- remove DMO to reply

hi,
Chase Preuninger wrote:
this is the italian localized NG for SQL Server, and questions should be
posted in italian..

your table is defined with a primary key on the Account_Name column..
primary key implies a unique value and this is the reason you can not insert
a duplicate for that column's value..
try defining another primary key instead the actual one.. you could perhaps
use an artificial key, perhaps based on a numeric column with an
autogenerated value like the Identity property provides..
read further about artificial keys in
http://www.intelligententerprise.com...leID=201806814
regards
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz http://www.hotelsole.com
DbaMgr2k ver 0.21.1 - DbaMgr ver 0.65.1 and further SQL Tools
--------- remove DMO to reply

oh, that is what the "it" menas sorry

oh, that is what the "it" menas sorry

oh, that is what the "it" menas sorry

On May 17, 7:48 am, "Andrea Montanari" <andrea.sql... (AT) virgilio (DOT) it>
wrote:
I am curious why you reference Joe's article but immediately suggest
an artificial key a the solution. The fact is, he already has an
artificial key (NOTE_ID). But if I were to change this I would change
the PK on the NOTES table to
note_owner, note_title, note_id
This seems a more natural key and it allows multiple note entries per
title and it allows different authors (owners) to contribute to the
same topic (title).

ED

On May 17, 7:48 am, "Andrea Montanari" <andrea.sql... (AT) virgilio (DOT) it>
wrote:
I am curious why you reference Joe's article but immediately suggest
an artificial key a the solution. The fact is, he already has an
artificial key (NOTE_ID). But if I were to change this I would change
the PK on the NOTES table to
note_owner, note_title, note_id
This seems a more natural key and it allows multiple note entries per
title and it allows different authors (owners) to contribute to the
same topic (title).

ED

On May 17, 7:48 am, "Andrea Montanari" <andrea.sql... (AT) virgilio (DOT) it>
wrote:
I am curious why you reference Joe's article but immediately suggest
an artificial key a the solution. The fact is, he already has an
artificial key (NOTE_ID). But if I were to change this I would change
the PK on the NOTES table to
note_owner, note_title, note_id
This seems a more natural key and it allows multiple note entries per
title and it allows different authors (owners) to contribute to the
same topic (title).

ED