After all these years, I finally get Error 999. ( Should be 666)
Took time to find as Vee closes auomatically without error message or BRB.
Bad programming of course but just for information, the culprit was
<<...OLE_Obj...>>
Dont know why....It works OK a couple of times in debug mode, but after
about 4 uses of this, it must get mixed up or something.
Suffice to say different outputs should be used extracting different parts
of a string, like so
<<...OLE_Obj...>>
Vee 6.0.3
Regards,
---
You are currently subscribed to vrf as: rsb@soco.agilent.com
To subscribe send a blank email to "join-vrf@it.lists.it.agilent.com".
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
Took time to find as Vee closes auomatically without error message or BRB.
Bad programming of course but just for information, the culprit was
<<...OLE_Obj...>>
Dont know why....It works OK a couple of times in debug mode, but after
about 4 uses of this, it must get mixed up or something.
Suffice to say different outputs should be used extracting different parts
of a string, like so
<<...OLE_Obj...>>
Vee 6.0.3
Regards,
---
You are currently subscribed to vrf as: rsb@soco.agilent.com
To subscribe send a blank email to "join-vrf@it.lists.it.agilent.com".
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
malfunctioned. The caution that your program may be corrupted is just a
general purpose caution. It means that parts of your program might have been
overwritten by the flailing microprocessor. That's why VEE won't let you
overwrite an existing file. The only way to tell is to save the possibly
corrupt version and compare it to a known good version.
In general there's nothing you can do about the problem. VEE will attempt to
pinpoint where serious problems developed, and you can try rearranging
things around that location to try to avoid the condition that caused VEE to
go wild in the first place.
-SHAWN-
---
You are currently subscribed to vrf as: rsb@soco.agilent.com
To subscribe send a blank email request to "join-vrf@lists.it.agilent.com".
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".