Hello Mark
Sometimes this error is caused by having a row with
blanks or nulls in the table key fields and when an insertion occurs it also
tries to insert blanks in the key fields.
Generally the error message relates to inserting an
row which has the same primary key as an existing row. So look at the data using
DBD32 and find a row which is the same as a row would be if the user inserted a
new row.
Regards
Russell
|
- [DUG]: Key Violation Mark Howard
- Re: [DUG]: Key Violation [EMAIL PROTECTED]
- Re: [DUG]: Key Violation Craig Goodall
- Re: [DUG]: Key Violation Mark Howard
- Re: [DUG]: Key Violation Nello Sestini
- RE: [DUG]: Key Violation James Sugrue
- Re: [DUG]: Key Violation Mark Howard
- RE: [DUG]: Key Violation Patrick Dunford
- Re[2]: [DUG]: Key Violation paul . mckenzie
- RE: [DUG]: Key Violation Stephen Barker