Re: Calling SQL*Plus from SQL*Forms (v2.3)

cs91dnm_at_brunel.ac.uk writes:
>
> Ideally I'd like them to be able to select an option from a menu which
> runs this SQL*Plus file without them having to log into SQL*Plus. At present
> my best thought (as yet untested) would be to have a #HOST SQLPLUS command in a
> trigger in a Menu Form. To say the least, this is ugly. Also the user would
> be forced to login twice. (once into the form, then again into SQL*Plus)
>

The customer should not have to login to SQL*Plus to run your script. If they do then maybe your DBA can correct this. The #HOST 'SQLPLUS -S / _at_myfile' should work just fine. This is the cleanest way to run SQLPLUS scripts/prgms from FoRMs.

> The other option I've though of would be to move all the code into a
> trigger (big trigger!) I think this could be tricky though for this reason.
> The SQL*Plus file uses SPOOL then SELECT to create a temporary file made up of
> more SQL commands (GRANTs in fact) and then runs that file.
>

Yuk! I know I have placed some large triggers in v2.3 before but never again. Talk about a maintenance headache! Even if you look at having to edit a complicated SELECT statement v2.3 the cut/paste/insert/delete options are not there.

What I have to do even with v3 is to run out to the host environment to edit trigger steps because modifications were easier but with v3 it is less frequent then with v2.3.

Good luck ... I would think your original thought on using #HOST commands are your best bet in keeping your FoRMs a little more maintenance free.

Mike Oswald
Univ. Of NE Medical Center
Computing Services/Telecomm Received on Tue Jul 27 1993 - 16:19:22 CEST