AnsweredAssumed Answered

vrf runtime execution of .vee?

Question asked by VRFuser on Dec 14, 2001
To make things somewhat more complicated: I was absolutely delighted when I
found out that I could even rename (!) the vxe-Files as vee-Files (without
changing the content, i.e. keeping the nice&small binary files) and still start
the VEE5-runtime directly with them. Which saved several hundred customers of
mine a lot of time. They all had an installation, in which V5-runtime was fed
with real old-style secured V3-vee-files, directly from the shortcut on the
desktop. Nothing had to be changed, just the secured-ASCII-V3 files (big) had to
be replaced by renamed V5-secured-runtime-vxe-files, which received the
extension *.vee.

Thomas Vauderwange


Richard Kleinhenz <scubaman@us.ibm.com>:

The .vxe files are the "secured" runtime files. The information
regarding how to construct the detail view is removed, so the end
user cannot see or change the program. Only the  panel view remains.
The .vxe can be binary or ascii, with binary being more secure (
you can still make minor mods to the ascii version if you are careful)

The intention is of course to create something you can run but not
change.

As you have seen, the runtime code can run any kind of VEE program- but
also note that it can't edit the code.

Stan

Richard Kleinhenz schrieb:

> I thought the runtime package needed .vxe files.  I have an application
> that calls other Vee programs, and during development, these were all .vee,
> naturally.  Now we pushed the app out to a bunch of lab machines, having
> only the runtime package installed.  And they run the .vee files fine.  I
> just tried opening .vee file with the runtime code, and indeed they open
> just the same.  Since .vxe is not required, what exactly is the purpose of
> .vxe files?  Are there some licensing issues?  One advantage is that .vxe
> is more compact than .vee.  Is that all?  And that it can't be edited with
> a text editor?  I have Vee 6.01, by the way.
>
> --
> Regards,
> Rich
> ===========================
> Richard Kleinhenz
> mailto:scubaman@us.ibm.com
> 845-892-2617
> ===========================
>
> ---------------------------------------------------------------------
> This is the "vrf" maillist, managed by Majordomo.  To send messages to
> this maillist, just email to "vrf@lvld.agilent.com".  Subscriptions and
> unsubscriptions are done through the address "vrf-request@lvld.agilent.com".
> If you need details, just send a message containing the text "help"
> to "vrf-request@lvld.agilent.com".
> ---------------------------------------------------------------------

---------------------------------------------------------------------
This is the "vrf" maillist, managed by Majordomo.  To send messages to
this maillist, just email to "vrf@lvld.agilent.com".  Subscriptions and
unsubscriptions are done through the address "vrf-request@lvld.agilent.com".
If you need details, just send a message containing the text "help"
to "vrf-request@lvld.agilent.com".
---------------------------------------------------------------------

Outcomes