SQL Problem

My friend,

This means that the column "ordersamples" has a primary key constraint, which means that this column cannot contain duplicate values.

You are trying to add a record to that table with a "ordersamples" value that already exists in the table, so either you remove the constraint (if you feel this column should accept duplicate values) or check the value you are entering.

Good Luck!

pjsinclair, what this is telling you is that you have primary key located over one of the fields in the ordersamples table I am not sure which field it is but if you look in the enterprise manager,under the design table you will see a key symbol over one or more fields, these are the primary keys, you are trying to insert a new row that has the same field contents as another row in the table that has a primary key defined for it.

You state that your are "accessing" a database (versus "inserting", "deleting" or "updating" data). Presuming that you are NOT intending to actually add a new record or changing data...

You also state that your are "accessing a field". But are you updating a "scratch" table within a database to view entries from other tables? If so...

1) Be sure you delete previous records before refreshing the table with a new "access" effort.
2) Preferentially, if using SQL2k, make use of temporary tables. These are more flexible in managing security issues and if you set these tables to be persistent to a specific user connection they'll automatically be cleared when the user connection is released.
3) Wouldn't accessing a specific field be better achieved by a query or view or SQL2k scalar function?

Alternate solution issue; are we actually dealing with a application (user control) bound to a database? Is your problem actually based on control having an inappropiate starting value that it is trying sync back to the database prior to pointing to a specific database record (ie. you are defaulting on the first (or a random) record on start up and the control is trying to sync the record to values present on the form.

Be sure that you haven't corrupted your database with an instance of this default value and be sure when bringing up a bound control that you are pointing to an appropiate database records (typically on form initialization, but before creating instances of controls at form load).

Your question could use some more details.

Insure you have an automatic incremeting primary key on the table.
This uniquely identifies each record as every record has to be different in a table

This question was closed by the author