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.
