AnsweredAssumed Answered

vrf AW: corrupted file

Question asked by VRFuser on Jan 26, 2004
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML><HEAD><META http-equiv=Content-Type content="text/html; charset=iso-8859-1"><META content="MSHTML 6.00.2600.0" name=GENERATOR></HEAD><BODY><DIV><SPAN class=513175215-26012004><FONT face=Arial color=#0000ff size=2>VEE is perfect in providing surprises from time to time.</FONT></SPAN></DIV><DIV><SPAN class=513175215-26012004><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV><DIV><SPAN class=513175215-26012004><FONT face=Arial color=#0000ff size=2>I made similar experience but do not know how this can be solved correctly and how this can be avoided. The reason why I respond to this request is to inform you about a very unfortunate behavior of VEE 6 and VEE 6.2.</FONT></SPAN></DIV><DIV><SPAN class=513175215-26012004><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV><DIV><SPAN class=513175215-26012004><FONT face=Arial color=#0000ff size=2>It may happen - and it happens from time to time - that during editing of a part of a VEE program, either modifications or amendments, that input and output ports of user functions are created automatically, although these user functions had not been on the active screen in this editing session. As a consequence, no longer you can run the program. Unfortunately, VEE does not precisely locate the problem. You have to check very detailed your program to find the location. Once you found the location it is easy to fix the problem.</FONT></SPAN></DIV><DIV><SPAN class=513175215-26012004><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV><DIV><SPAN class=513175215-26012004><FONT face=Arial color=#0000ff size=2>In addition, it might be that after successful correction still the program is not running, i.e. still showing the same error message. Then it may help just to store the file and re-open it.</FONT></SPAN></DIV><DIV><SPAN class=513175215-26012004><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV><DIV><SPAN class=513175215-26012004><FONT face=Arial color=#0000ff size=2>This is fun!</FONT></SPAN></DIV><DIV><SPAN class=513175215-26012004><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV><DIV><SPAN class=513175215-26012004><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV><DIV><SPAN class=513175215-26012004><FONT face=Arial color=#0000ff size=2>Hans-Joachim Fischer</FONT></SPAN></DIV><BLOCKQUOTE>  <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma   size=2>-----Ursprngliche Nachricht-----<BR><B>Von:</B> Ivan Edwards   [mailto:ie@irisys.co.uk]<BR><B>Gesendet:</B> Montag, 26. Januar 2004   16:21<BR><B>An:</B> VRF<BR><B>Betreff:</B> [vrf] corrupted   file<BR><B>Wichtigkeit:</B> Hoch<BR><BR></FONT></DIV>  <DIV><FONT face=Arial size=2><SPAN class=113370815-26012004>Over the past two   years I have developed a test program which has grown to over 3Mbyte   in size and there are many tens of user objects and user functions in   it.  Of late I have had the odd instance of the dreaded red 'corrupted   file' screen occurring during operation of the .vxe.  I have found on   investigation that a small user function written long ago now has a strange   behaviour.  Some functions within it have missing connections at their   input, yet they continue to work!  Also the main output of the user   function cannot be deleted without the corrupted file' screen coming up.    Looking back through earlier versions it appears to have crept in about 6   versions ago without any warning that I can recollect.  I have deleted   the user function and copied in a new version.  For the moment I believe   all is well, though time will tell as the corrupted version worked OK 99% of   the time anyway.</SPAN></FONT></DIV>  <DIV><FONT face=Arial size=2><SPAN   class=113370815-26012004></SPAN></FONT> </DIV>  <DIV><FONT face=Arial size=2><SPAN class=113370815-26012004>My question is,   how can I be sure that there aren't other nasties like this buried somewhere   in my program?  Has anyone similar stories to tell?  What could I do   differently to make sure corruptions don't take place or at least are spotted   as soon as they do occur?</SPAN></FONT></DIV>  <P><FONT face="Courier New" size=2>Ivan Edwards</FONT> </P>  <P><FONT face="Courier New" size=2>Senior Engineer,</FONT> <BR><FONT   face="Courier New" size=2>InfraRed Integrated Systems Ltd.,</FONT> <BR><FONT   face="Courier New" size=2>Towcester Mill,</FONT> <BR><FONT face="Courier New"   size=2>Towcester,</FONT> <BR><FONT face="Courier New" size=2>Northants   (UK).</FONT> <BR><FONT face="Courier New" size=2>NN12 6AD.</FONT> </P>  <P><FONT face="Courier New" size=2>Tel:   +44 (0)1327 357824</FONT>   <BR><FONT face="Courier New" size=2>Fax:   +44 (0)1327 357825</FONT>   <BR><FONT face="Courier New" size=2>Website: www.irisys.co.uk</FONT>   <BR></P>---<BR>You are currently subscribed to vrf as: vee@esf-gmbh.de<BR>To   subscribe send a blank email to "join-vrf@it.lists.it.agilent.com".<BR>To   unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".<BR>To   send messages to this mailing list, email "vrf@agilent.com". <BR>If you need   help with the mailing list send a message to   "owner-vrf@it.lists.it.agilent.com".<BR>Send your favorite VEE example to   "VRF-EXAMPLES@agilent.com" for possible inclusion in VEE 7.0! </BLOCKQUOTE>---<BR>You are currently subscribed to vrf as: rsb@soco.agilent.com<BR>To subscribe send a blank email to "join-vrf@it.lists.it.agilent.com".<BR>To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".<BR>To send messages to this mailing list,  email "vrf@agilent.com".  <BR>If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".<BR>Send your favorite VEE example to "VRF-EXAMPLES@agilent.com" for possible inclusion in VEE 7.0!</BODY></HTML>  

Outcomes