Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
FP26 reports crashing in VFP
Message
From
09/10/2018 13:15:42
 
 
To
09/10/2018 08:12:40
General information
Forum:
Visual FoxPro
Category:
Reports & Report designer
Environment versions
Visual FoxPro:
VFP 9 SP2
OS:
Windows 7
Miscellaneous
Thread ID:
01662501
Message ID:
01662524
Views:
52
>>I'm running into a weird issue on a client project. This is a large vertical market application that has a ton of reports created in FP2.6/Win that need to run in the VFP version of the application that we're creating. For the moment, we cannot convert them to VFP because they have to run in both versions.
>>
>>On one of my machines, but not the other, when I run the reports in the VFP IDE, VFP crashes. I've confirmed via the Debugger that it's definitely happening in the REPORT FORM command, not in the code that precedes that. This happens when I run the report through the application or by setting up the data outside the application and then issuing REPORT FORM directly from the Command Window. If I convert the report to a VFP report, the problem goes away, but as I said, that's not a viable solution for now. And because of that, I can't see if I get more info by doing MODI REPO and then previewing
>>
>>I tried clearing printer information from the report, but that doesn't solve the problem. I also tried changing the default printer on this machine, but no go either.
>>
>>The machine that fails is running Windows 7 Build 7601. The machine that works is running Windows 10 and is fully up-to-date.
>>
>>It's a C5 error. I've tested with several different reports, so unlikely to be the report itself or the underlying tables (and a cursor is created before running the report).
>>
>>Open to ideas for what this could be.
>>
>>Tamar
>
>I do recall running into conflicts with some printer drivers and FPW (basically having to do with how memory was being handled by the DOS Extender used in the runtime) -- using a different printer driver (usually one for an older model). was one of the workarounds -- the trick being that you have it appear as a different printer within Windows.

But wouldn't having a different printer set as Default in the first place (and I tried Generic/Text) solve the problem?

It occurs to me that I should say the REPORT FORM command includes PROMPT, but the crash occurs before the printer dialog appears.

Tamar
Previous
Reply
Map
View

Click here to load this message in the networking platform