@once problem

[Richard Kreiss]

> -----Original Message-----
> From: filepro-list-bounces+rkreiss=verizon.net at lists.celestial.com
> [mailto:filepro-list-bounces+rkreiss=verizon.net at lists.celestial.com] On
> Behalf Of Kenneth Brody
> Sent: Monday, October 14, 2013 11:38 AM
> To: Jay Ashworth; filepro-list at lists.celestial.com
> Subject: Re: @once problem
> 
> On 10/13/2013 1:40 PM, Jay Ashworth wrote:
> > Unless I'm greatly mistaken, there's no way to tell between a deleted
> > record and an empty one in dclerk -- that is, it could be deleted, and
> > if you said "Record 1", you wouldn't know.
> 
> Well, there are several ways to tell.  One simple way is to put @CD on the
> screen.  (Deleted records have a blank @CD.)  Another would be to scan for
> @RN equal to "1".  (It won't find it if record 1 is deleted.)  There are
others,
> but these should get you started if you really wanted to look for more.
> 
> --
> Kenneth Brody

Ken, the  answer to your question, I built a demand index on record # on
this file and no records were selected.  I also did an extended scan for
records with @rn="1".  Again, nothing found.

There are other programs that run from my library file that use @once in
report and are not experiencing this problem.

The only problem that has cropped up in some of the programs is the passing
of exit codes which are not being passed to the batch file which started the
program.

 I first noticed the problem with the program in question  which had an exit
code of "99" which was set if no file name was present.  The batch file
should have gone to the subroutine done but didn't.  My client mentioned
today that another @done routine from another program which moves specific
pdf files created to specific folders is not working.

As these programs have been working for over 2 years, I am wondering is a
recent update to the Windows OS may be causing this problem or if it might
be their anti-virus program.

Richard