This is probably super basic but I've never built a procedure where I'm writing to a table where I need to pull the next id. Can someone walk me through how to find the next id, assign it on the insert, and then make sure that the next id table gets updated?
Thanks in advance!
Gawain Lavers you say that like that is not true of all of us.
For me the key difference is the persistence of temp tables outside of the local context. I do wind up having a number of applications where I want to share data between different stored procedures running in the same session.
John A. Moskal II Gawain Lavers either of you up for helping a gal out and looking at some SQL?! I have a procedure all built and running and we've just now realized that every once in a while there is a funk thing happening. I'm copying information into a research note from another table and it creates a random second note that has the same cust_notes_no as the one before it with incorrect information that seems to be pulling from another record but I haven't been able to establish where or why it's happening. When I run the procedure to check it out I cannot get it to recreate the issue.
Sure, hit me.
Thanks. Just sent you a message.
Was out of the office already. Madeline Dummerth (Past Member), I assume Gawain Lavers has you covered. If not, feel free to hit me up.
All good, thanks! So I *think* it's been solved but I'm going to monitor it for a few days and see if the issue crops up again.
In addition to the wisdom shared above, please also see:
https://community.tessituranetwork.com/tessitura_software_forums/f/tessitura_technical-9/1621/procedure-frustration/5663
A classic code example for generating multiple Tess IDs, reputedly from Chuck R himself.