AnsweredAssumed Answered

VRf-VXE_VEE.IO

Question asked by VRFuser on Aug 16, 1997
send q VRf-VXE_VEE.IO ww vrf JeffTEF_Davis-P25691@email.mot.com

from: Greg Goebel / HP-MXD
      gvg@lvld.hp.com / 970-679-3030 / FAX 970-679-5971
      website:  ftp://fcext3.external.hp.com/dist/mxd/index.html
to:   VRf-Jeff Davis
date: Sunday, 17 August 1997 1148 MDT

> Date: Fri, 1 Aug 1997 9:04:32 -0500
> From: JeffTEF Davis-P25691 <JeffTEF_Davis-P25691@email.mot.com>
> Subject: VRF - vee command line options
> To: hpvxd_xc@hpislsup.lvld.hp.com
>
> I have been attempting to use the command line option <-veeio> to cause vee
> to use an io config file other than the normal (original) one.
> I have been successful doing this with the development copy of vee but when
> I try doing the same thing with the .vxe file, the normal veeio file is
> accessed and not the custom one that was created. Is this functionality
> possible with the executable files?
>
> Let us know?

Sir:

Sorry I'm running late ... here's what I think the answer is:

--------------------------------- cut here ----------------------------------



[VEE] COMMAND LINE OPTIONS & VEE RUNTIME

* With VEE 4.X, a new runtime scheme was introduced to make a VEE program
look as much like an executable program as possible.  The user can save
secured VEE programs with a .VXE (VEE eXEcutable) extension; when these
programs are selected under Windows, they are automatically executed -- by
way of an "association" to the "veerun.exe" file set up when VEE is
installed.

This arrangement can be a little confusing.  A VEE user wanted to use a
command-line option -- the "-veeio <filename>" option, which allows the user
to specify an alternate VEE I/O configuration file -- and found out that it
worked for the original .VEE file but not for the run-time .VXE file.

This turned out to be a somewhat confusing configuration issue.  For program
development, a user invokes the "vee.exe" file through the Windows start menu
or a shortcut; it is simple to modify either to add the "-veeio <filename>"
option, and this works fine for program development.

Once saved as a .VXE file, however, the program is then executed by
"veerun.exe" automatically through the file association ... and so the same
option has to be applied to "veerun.exe".

The appropriate changes can be made through either Windows Explorer or
Windows MyComputer ... just select:

   View -> Options -> File Types

-- then find "HP VEE Executable" and "Edit" that entry ... you will get a
list of selections with "open" as the only entry, so "Edit" that in turn.

This gives an invocation of "veerun.exe" that can be modified to add the
"-veeio <filename>" option.  From that point on, all invocations of .VXE
files from Windows will use that VEE I/O configuration file.

Outcomes