Exactly the steps I took. Just did it again. I am the only one connected to a localdatabase altho multi is on. The SP is used in a trigger, as shown in my print-screen.
Edited the SP source, hit a space bar, the first "OK" clicked is fine. When I click the final "OK" to exit the SP edit screen, I get the error message. I eventually got it to accept a change with some combination of setting multi off,dropping the trigger, can't remember what, but it took a few steps. Karen -----Original Message----- From: A. Razzak Memon <[email protected]> To: [email protected] Sent: Mon, Mar 8, 2021 9:14 am Subject: Re: [RBASE-L] - Tip of the Day: Enhanced UNLOAD Output for Stored Procedures Here are proper steps to "Edit Source" of existing Stored Procedure ... See attached. Very Best R:egards, Razzak At 09:57 AM 3/8/2021, 'Karen Tellef' via RBASE-L wrote: >Speaking of SPs. I needed to make a small change to a SP that is >used as a Trigger. It seemed to accept the change, I clicked "OK" >to exit the SP screen and got an error message "invalid column >name". Tried again, and just doing something like hitting a >spacebar and then deleting it would generate the same message. > >I'm guessing that's because others were in the database or because >it was in a trigger? Later I got the database single-user, I had to >delete the trigger, then change the SP and reinstall the >trigger. Is that the proper way to do it? > >Karen > >-----Original Message----- >From: A. Razzak Memon <[email protected]> >To: [email protected] >Sent: Mon, Mar 8, 2021 8:37 am >Subject: [RBASE-L] - Tip of the Day: Enhanced UNLOAD Output for >Stored Procedures > >Monday, March 08, 2021 > >Tip of the Day: Enhanced UNLOAD Output for Stored Procedures >Product.......: R:BASE X.5 and R:BASE X.5 Enterprise (Version 10.5) >Build.........: 10.5.3.20304 or higher >Sections......: Commands >Keywords......: UNLOAD, STRUCTURE, DATA, Stored Procedure > >Did you know that the UNLOAD STRUCTURE and UNLOAD DATA commands >were enhanced with the generated output, where stored procedure >data is now placed in the structure output? > >The UNLOAD STRUCTURE output now includes stored procedure data, >before triggers, allowing the file output from subsequent UNLOAD >STRUCTURE and UNLOAD DATA processes to be utilized for database >rebuilds. With this change, stored procedure data is not unloaded >as part of the data unload. > >Also, when performing an UNLOAD ALL, you will now see the procedure >data in its new location (right before triggers) rather than in the >middle of the data for all the other tables. > >If your output is going to the SCREEN, rather than a file, and you >do an UNLOAD which requires LOB output, a SCREEN.LOB file will be >created in the current directory. > >The end result allows database with stored procedures to be easily >rebuild from the separated UNLOAD STRUCTURE and UNLOAD DATA output, >which is helpful in database maintenance! > >Very Best R:egards, > >Razzak. > >https://www.rbase.com >http://www.facebook.com/rbase/ -- For group guidelines, visit http://www.rbase.com/support/usersgroup_guidelines.php --- You received this message because you are subscribed to the Google Groups "RBASE-L" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/rbase-l/1MyKcC-1lgYdI2X1g-00yjDI%40mrelay.perfora.net. -- For group guidelines, visit http://www.rbase.com/support/usersgroup_guidelines.php --- You received this message because you are subscribed to the Google Groups "RBASE-L" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/rbase-l/804634377.490400.1615217226580%40mail.yahoo.com.
