Generating Output Count

George Simon GSimon at americanriverintl.com
Thu Dec 3 08:54:55 PST 2009


I neglected to mention that I also moved all the customer's data to my computer and was able to run the statements from there without any errors, 100% of the time.  Maybe is a combination of things.  One thing is for sure, it did not happen just to you.  Also, the only other 2 things in common are filePro and Windows Server 2003.

-----Original Message-----
From: Nancy Palmquist [mailto:nlp at vss3.com] 
Sent: Thursday, December 03, 2009 11:43 AM
To: George Simon
Cc: Kenneth Brody; filepro-list at lists.celestial.com
Subject: Re: Generating Output Count

George Simon wrote:
> I've had the same problem at one customer.  Also running Windows Server 2003 and filePro 5.0.14.
> This program, (part of a vertical application) generates monthly statements. It is running perfectly in many other locations, most of them also running Windows Server 2003.  The program would select the correct amount of records and then exit without warning before finishing.  It did not always happen at the same record count.  Sometimes it would only print a couple of the selected records and exit.  Other times it would print 90% and then exit.  I tried to solve the problem for many months, even going to the customer's site and running the statements myself to make sure everything was being done properly, but I was never able to figure out what was causing it to exit without warning.  It made the running of the monthly statements a nightmare.  So bad in fact that the customer, after running my software for over 10 years, gave up and moved to something else.  I could not blame him one bit as I would have done the same thing.
> One thing I did notice was that when I sent the output to a file, instead of the printer, the problem did not occur as often but it would still occur.
>   
George,

I have run the process 10 times today, and no failure or strangeness at 
all.  Except one.

I had 1 occurrence crash and say the rp{00000 was invalid.  When I 
started a second occurrence that was running on a different file.  I 
looked in the temp folder and it looked to me like the second occurrence 
used the same rp{00000 file to write its index, and that messed up the 
other report.

Have repeated many times today, and no other issue.  I did clear out the 
temp folder, so maybe it hit the last character it can put in the rp 
name or something and repeated.  I can only guess.

Nancy

-- 
Nancy Palmquist 		MOS & filePro Training Available
Virtual Software Systems	Web Based Training and Consulting	
PHONE: (412) 835-9417		   Web site:  http://www.vss3.com




More information about the Filepro-list mailing list