| Calling SQL scripts from Forms in app server environment [message #634702] |
Fri, 13 March 2015 09:31  |
joy_division
Messages: 4963
Registered: February 2005
Location: East Coast USA
|
Senior Member |
|
|
I'd like to know how people are calling SQL scripts from Forms on an app server, especially those that require user inputs via the PROMPT command.
We are using a method which I do not like and one day I'd like to change it.
We read in the script, parse for any lines with a PROMPT command, have the user enter the values and then HOST out to call SQL*Plus to execute the script.
I don't like it. I don't like it one bit. It was written way before I got here and never had the time to look at an alternative method.
Any thoughts?
[Updated on: Fri, 13 March 2015 09:32] Report message to a moderator |
|
|
|
|
|
| Re: Calling SQL scripts from Forms in app server environment [message #634845 is a reply to message #634837] |
Mon, 16 March 2015 13:07  |
joy_division
Messages: 4963
Registered: February 2005
Location: East Coast USA
|
Senior Member |
|
|
Yes, good question Craig, but these are legacy SQL scripts that run a report based on multiple prompt statements, which produces output that the user then sends to a printer. If it just weren't for the output that is needed...
There are hundreds or these little reports and rather than rewrite them all, someone came up with the idea (and it was pretty cool at the time) to read in the script, parse out all the PROMPT statements and have the user enter them as parameters, then call SQL*Plus to run the scripts with the parameters on a command line.
I want to change this, but have the same issue. I do not want to rewrite hundreds of unique SQL scripts.
|
|
|
|
|
|
| Re: Calling SQL scripts from Forms in app server environment [message #634883 is a reply to message #634882] |
Tue, 17 March 2015 08:28 |
joy_division
Messages: 4963
Registered: February 2005
Location: East Coast USA
|
Senior Member |
|
|
CraigB wrote on Tue, 17 March 2015 09:11
You are the only person I've heard of that is doing this. One of the projects I was working on was using HOST to call Pro-C report scripts, but the parameters were "Hard Coded" so we didn't have to parse anything.
Hahaha, I know. go figure, I come to this company with a proprietary application that one day is going to blow up because it won't work when "something changes."
Quote:
Sorry I couldn't be more helpful.
To the contrary, it just confirms what i thought has to be done.
I just have to solve how to run SQL scripts that produce output and get it to the printer without having to rewrite them as RDFs.
Thanks.
|
|
|
|
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
I understand your aversion to rewriting the scripts, but maybe now is the time. 
Of course, once things start going that's a different matter!