Buddy, It tried using the UNC, but no difference in results. An inserted record from an Rbase session, the trigger/stored procedure displays the file. A record from the Oterro session does not. Thanks for the idea though.
----- Original Message ----- From: Bob Thompson To: RBASE-L Mailing List Sent: Wed, 12 Jun 2013 04:41:46 -0000 (UTC) Subject: [RBASE-L] - RE: Oterro / Stored Procedure question I have not, but it is where the database resides and the rest of the stored procedure is working. However I will give it a try first thing in the morning. The exact same trigger works if data is inserted via an Rbase session, so I would not think it is connected to the path. But I certainly will try it out. Anything to get this into production Thanks for the suggestion. Bob Thompson LaPorte, IN 219-363-7441 Sent from my iPod On Jun 11, 2013, at 5:21 PM, "Buddy" <[email protected]> wrote: Tom Have you tried using the UNC instead of the mapped drive letter Buddy From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Tuesday, June 11, 2013 5: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.
