Thread View: borland.public.intrabuilder.data.sql
1 messages
1 total messages
Started by Billy Hildebrand
Thu, 08 Jan 1998 00:00
UNIQUE KEY constraint
Author: Billy Hildebrand
Date: Thu, 08 Jan 1998 00:00
Date: Thu, 08 Jan 1998 00:00
33 lines
1702 bytes
1702 bytes
I have a form I use to edit customer profiles that uses loops to build a series of text and select boxes. The select boxes are populated through a series of SQL calls to an InterBase server. There are three areas composed of five select boxes and a corresponding text box for each. Input on two[ second and third area ] of these works. User can select an entry from one or more select boxes and type in additional information in the text box. [example: select credit card company: Visa, MasterCard, etc, enter card number in text box]. Here's the problem: Whenever the first area has 2-4 [1 or all 5 completed works] selections and corresponding fields filled in And submitted I get the following error: Server Error: violation of PRIMARY or UNIQUE KEY constraint "INTEG_120" on table "TABLENAME" I really don't understand why my method doesn't work on all three areas since all three are built in the same way [and same function call] and all three have basically the database structure [areas two and three have an additional field]. I have searched help and found "keyViolationTableName" as a property to the UpdateSet class, but no example or explanation on how to set this property. Can anyone help with this? Billy Hildebrand Webmaster WWTS
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads