Debug Error! Microsoft Visual C++

[Boaz Bezborodko]

I know that it's now PW, since I've now verified that the process never 
gets to that point.

At some point it opens a control file to get a unique number.  When it 
gets to the command "CLOSE file" is when the error occurs.

All the PCs here are nearly identical HP boxes.  I set them all up at 
the same time.  But the problem shouldn't be there in the first place.

I'll contact fpsupport.

Boaz

On 6/4/2015 2:11 PM, Kenneth Brody wrote:
> On 6/3/2015 12:48 PM, Boaz Bezborodko via Filepro-list wrote:
>> I'm running a report that prints to a file before having the file 
>> copied and
>> then passed on to a print queue serving Bob Rasmussen's Printwizard 
>> in order
>> to generate a PDF.
>>
>> On one computer I was getting a Windows Visual C++ error at the count 
>> down
>> to '0' records:
>> "Debug Error!
>>
>> Program: h:\fpro\fp\rreport.exe
>>
>> DAMAGE after Normal block (#1009) at 0x0086A2E0.
>>
>> (Press Retry to debug the appication.)"
>>
>> The rp.... file still exists and file generated seems to be OK as 
>> well. The
>> error occurs in a called routine that does the copying and printing, BUT
>> ONLY for one particular report that calls this routine.  When other 
>> reports
>> call this routine they work fine.  This happens with most of the 
>> computers
>> on my network.  And when I run it with dreport instead of rreport it 
>> works
>> fine on those computers. But there is another computer that has the 
>> exact
>> opposite result. It works fine with rreport, but errors out when run 
>> with
>> dreport.
>>
>> I'm using 5.6.10R9 on Windows.
>
> Can you simplify things, and send the output directly to a file? (It 
> shouldn't matter, but let's eliminate PW as a possibility.)
>
> Since you say it only happens on this one report, you should contact 
> fpsupport and arrange to send files so it can be duplicated in-house.
>


---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus