You’re offline. This is a read only version of the page.
I converted our GP9 to GP2010 over the weekend and MUCH to my dismay, found out Microsoft got rid of my custom triggers that we've had on Vend/Cust MSTR tables since version 6!!!
I have a master list of customers and vendors that's shared between (now) 42 companies and the triggers inserted them into each database. It's the PM00200 and PM00300, and RM00101, 102 and 103. The way they were coded, the trigger itself did the insert (ie.. insert into <Co>..RM00101(..) select ... from inserted;)
In talking with our partner, they suggested moving the code to a custom database (which I already have procs there) and having the trigger on the 'MASTER' company invoke the proc in custom.
OK - so I did it, but now when I go to save off the vendor screen it tells me a "cursor already exists" and names the cursor. The cursor is in the custom database and loops thru SY1500 so the insert goes to all the companies. The procs look fine to me, and I've run the sql generated just to see if the syntax was fine, which it is.
Any clues? This doesn't seem to be rocket science.
*This post is locked for comments
If your triggers are hard to manage, there is always the Master records triggers in the PSTL tools library. They can be used to sync Customers and Vendors across GP companies.
Found out what was happening: In programming the triggers, I ran in the test company. Those triggers weren't disabled and so I got the "trigger firing the trigger" thing.
Sorry to be a bother.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,240
Super User 2024 Season 2
#2
Martin Dráb
230,149
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (