I usually make sure to update the infamous T_NEXT_ID table when I make bulk inserts into T_PHONE or T_ADDRESS, but recently we're having trouble with our website API, which gives us the following error when a user tries to register:
System.Data.SqlClient.SqlException: Violation of PRIMARY KEY constraint 'PK_T_EADDRESS'. Cannot insert duplicate key in object 'dbo.t_eaddress'.
Failed on Insert of T_EADDRESS
The statement has been terminated.
at Tessitura.WebAPI.Tessitura.Register(String sSessionKey, String sUID, String sPwd, Int32 iLoginType, String sEmail, String sFName, String sLName)
--- End of inner exception stack trace ---
T_EADDRESS does not appear as a table in T_NEXT_ID and therefore, to my reckoning, T_NEXT_ID doesn't need to be updated as far as the max(eaddress_no). Any ideas? Or is this a TASK situation?
Thank you for your assistance, Tessiturians.
Los Trivialos: The character of Optimus Prime on the popular 1980s animated television series "Transformers" was originally written to speak with a Jamaican accent.
If I recall correctly, t_eaddress uses the same ID as t_address. You may want to open a Task ticket for help on this one.
-steve carlock
Information Technology Manager
The Granada
(805) 899-3000 x 111 (phone)
(805) 899-3081 (fax)
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Matt Gonzales Sent: Tuesday, February 16, 2010 11:52 AM To: Steve Carlock Subject: [Tessitura Technical Forum] EADDRESS trouble
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!