AnsweredAssumed Answered

vrf VEE 6.01 Fatal Error

Question asked by VRFuser on Apr 12, 2002
When Vee won't open some files, I use Wordpad as well.  Sometimes Vee forget
to put a bracket "]" in the proper place.  I manually add the appropriate
character and can usually bring up the file.  Sometimes however it cuts off
the file and forgets to save an entire section, then I can only go to the
backup.

Sincerely and God Bless,

Bill Fisher
Computer Marketing Services


----- Original Message -----
From: "Pat Vittorini" <pvittorini@rim.net>
To: <Bill_Karnavas@transarc.com>
Cc: "VEE Users Group (E-mail)" <vrf@lvld.agilent.com>
Sent: Friday, April 12, 2002 7:21 AM
Subject: RE: vrf VEE 6.01 Fatal Error


> Words to live by.
> On the odd time that a program  becomes corrupted and won't open, I open
the
> ".bak" file in notepad or wordpad and save it as a ".vee" file. This has
> worked many times and saved me the frustration of having to redo the older
> version.
>
> -----Original Message-----
> From: Bill_Karnavas@transarc.com [mailto:Bill_Karnavas@transarc.com]
> Sent: Friday, April 12, 2002 7:37 AM
> To: vrf@lvld.agilent.com
> Subject: Re: vrf VEE 6.01 Fatal Error
>
>
>
> Just a couple comments on safe coding.
>
> I've been working with VEE for a few years now and it is not perfect,
> and will occasional eat a file.
> There are a couple practices that you can do to minimize the impact of
> these problems and generally improve your coding style.
>
> 1) Most important and already mentioned here, is to not keep saving to
> the same file.  I tack a number on the end of my root file name and
> increment it as I go.  I rarely work more than half an hour before
> saving to a new numbered file.
>
> 2) Going along with version numbers, I keep a notepad going in each
> file which comments on what I have been working on and is new or
> changed in each version.  If a version becomes corrupted, by vee or
> disk, I can often look at the comments (using a text editor) and
> recall most of what was lost in that revision.
>
> 3) Keep code files reasonably sized.  This was probably a factor in
> the original post on this, in my opinion, where the file was around
> 2MB.  It is just good programming style to break large projects up
> into smaller groups of related functions, usually refered to as
> modules.  There are lots of good programming reasons to do this, like
> making code reuse more practical and testing possible.  In many of my
> own projects I find that there is a test as a whole that is run, but
> many times there is a need to run some part of an analysis outside of
> the whole and then taking that module and giving it a new front end
> makes for some real quick development of a new program that makes me
> look good.  I try to keep modules down to 200-300K.  Working on
> modules much bigger seems to bog down and the risk in code loss due to
> corrupt file goes up a lot.
>
> lBill
> ---------------------------------------------------------------------
> 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".
> ---------------------------------------------------------------------

---------------------------------------------------------------------
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