Hello VEE people,
I have a problem in acquiring the date/time in a VEE program. I am
using the now() function in an 'Until break' loop in order for me to
CONTINUOUSLY acquire the time/date. Currently, the now() function is
fed to an alphanumeric display. My problem is that for every 'Until
break' loop, the alphanumeric display acquires a new time/date from
now(), and consequently the display 'flickers'.
Can anybody suggest a remedy to stop the flicker?
Thanks,
Tom Evans,
evanstr60@hotmail.com.
Ellison Sensors International,
Wrexham,
Wales,
UK.
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
I have a problem in acquiring the date/time in a VEE program. I am
using the now() function in an 'Until break' loop in order for me to
CONTINUOUSLY acquire the time/date. Currently, the now() function is
fed to an alphanumeric display. My problem is that for every 'Until
break' loop, the alphanumeric display acquires a new time/date from
now(), and consequently the display 'flickers'.
Can anybody suggest a remedy to stop the flicker?
Thanks,
Tom Evans,
evanstr60@hotmail.com.
Ellison Sensors International,
Wrexham,
Wales,
UK.
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
I volunteered to write a quick and dirty VEE program to parse some v.large
data files and extract some statistical information. Because each group of
records in the file can have different "structures" to them, using an off-
the-shelf extraction program wouldn't work (like Monarch). Besides VEE is
pretty good at dealing with files, strings, and simple statistics, right?
Problem #1: When I read using TOKEN excluding a comma "," it skips over
consecutive commas treating them as 1. In a comma delimited data file, this
is disastrous. Greg, I know the book points this out as a feature, but can
we possibly get a switch somehow to turn it off? I need a NULL string
returned for each consecutive comma. Any suggested work-around?
Problem #2: After reading a few tokens from a line of data, I'll see that
the rest of the line can be skipped. READ TEXT null TOKEN EXCLUDE:"
" was
used to blow off the rest of the line. It worked, EXCEPT when I follow that
with a READ TEXT x INT hoping to read the INTEGER at the beginning of the
next line. It will only read the first digit of the integer and move the
file pointer one byte. Is this a known bug? A work around for ME is to use
READ TEXT null STR to skip to the next line. This wont work for everyone.
Problem #3: This is going to be tough to track down. It's very similar to
#2, only it occurs pseudo randomly in the middle of the file I'm reading.
Every so often the data gets "out of sync" and it's because of a READ TOKEN
EXCLUDE:"," command that failed to read all the way to the next comma. It's
not at the end of a line like #2 and so far I can't find what DOES trigger
it to fail.
Suggestions are welcome. (I know, don't volunteer!)
Anyone have similar problems, or know of situations where reading by tokens
doesn't always work?
Thanks,
Mike Groves
R&D Engineering
Ericsson Inc.
Morgan Hill, Ca
mike.groves@ericsson.com