Here's a suggestion from way out in left field... Rather than having the launch right in the stored procedure, can you have the stored procedure run an outside program whose one line is just the launch? See if that fools it?
Karen -----Original Message----- From: Bob Thompson <[email protected]> To: RBASE-L Mailing List <[email protected]> Sent: Tue, Jun 11, 2013 11:38 pm Subject: [RBASE-L] - RE: Oterro / Stored Procedure question I have messages turned on. But part of the issue is that Oterro does not have a display to show messages. ( it is not intended to by design I think) World Ship is the program that is running. It exports data into an Rbase Data base via Oterro. There is no R> or screen console with Oterro. The trigger / stored procedure with launch works as expected if I enter data into the table from Rbase. The trigger/stored procedure runs when data is entered by World Ship. There is significant processing going on in the stored procedure. It all works except the Launch command. Again only via Oterro. The Launch command works if the trigger is fired by an Rbase session insert I had tried the command variable approach but results were the same. My whole project works as I need except I MUST be able to display a message to the World Ship user in real time. I would use other methods if I could devise one. Thanks for the response Bob Thompson LaPorte, IN 219-363-7441 Sent from my iPod On Jun 11, 2013, at 4:52 PM, "Javier Valencia" <[email protected]> wrote: Have you tried tracing the process to makes sure if the LAUNCH command itself is not executing or if it aborting before then? Have you tried turning messages and error messages on to see if you get nay warnings? Also, I have had luck in the past creating the command as variable and using it with the LAUNCH command: Instead of: Launch G:\RBTI\UPS\ErrorDoc.pdf Use: SET VAR vMyLaunch TEXT = ‘G:\RBTI\UPS\ErrorDoc.pdf’ LAUNCH &vMyLaunch Javier, Javier Valencia, PE O: 913-829-0888 H: 913-397-9605 C: 913-915-3137 From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Tuesday, June 11, 2013 4:04 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Oterro / Stored Procedure question One of those days.. :( I have an urgent project with a very short time constraint and am not having much luck today. What's new in Oterro 8 lists : 1.2 R:BASE Turbo V-8 Fully compatible with R:BASE Turbo V-8 specific enhancements · New #NOW System Variable · Support for Stored Procedures and AFTER Triggers · Support for LAUNCH Command · Support for LAUNCH Command in Stored Procedure/Triggers However I cannot get LAUNCH to work in an insert trigger with Oterro. If I add a record to the triggered table from the R> with an insert command, the stored procedure runs and the LAUNCH command in the stored procedure works as expected. When Oterro adds a record to the same table, the store procedure does run, but the Launch command does not execute. My command is : Launch G:\RBTI\UPS\ErrorDoc.pdf Is my syntax correct? (the .pdf extension is correct as it works from the R> insert) I have also tried other document formats such as jpg etc. I have an absolute requirement to display a screen message if certain data requirements are not met with the Oterro foreign data insert. I can collect and test the data, in the stored procedure/trigger, but have not found a way to display the screen message. When Oterro inserts a record, data is checked and if not correct, the message must display real time on the monitor of the processing computer. Any other possible, reasonably quick solutions? I am hoping I am missing something with the above syntax with Oterro. The Launch command would be perfect if I can figure it out. Otherwise, I have found no other way to display this message. Thanks, it is much appreciated.
