Output table freezing

Mike Schwartz filepromike at gmail.com
Tue Dec 19 09:40:54 PST 2017


> Hello to everyone. Happy Hanukkah Merry Christmas I am running Fileprp
> 5.0.14 on a Server running Windows 2013 operating system.
> Filepro is on a mapped drive to my desktop running Windows 7.
> I have a Filepro database that uses an alien file that is deleted and
> downloaded for each run. All of my other tables in this file run fine.
> The table that is stopping without an error, just stalls at different points is 264
> lines long with 12500 records.
> I thought it was looping somewhere and ran it in debug mode.  It ran fine in
> debug mode. Problem is it will take 20 hours to run the table in debug mode.
> I am at a loss. Any thoughts would be greatly appreciated.
> Thanks
> 
> Rich Tartaglia

     I suggest putting some LOGTEXT messages into the processing table.  The LOGTEXT message should include the record number and whatever else you think you need to debug it.  Be sure to set the LOGFILE variable before you call the table, so that you know where to find the LOGTEXT output file.

     Just be looking at the length of the LOGFILE, you can see if it is stopping at the same place in the code.  

     Once you know how many records are getting processed, you can use some logic to turn on debugging just before you hit that point in processing.

Mike Schwartz






More information about the Filepro-list mailing list