Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Fatal Error / C5 on REPORT FORM TO PRINTER PROMPT PREVIE
Message
From
15/01/2005 22:18:29
 
 
To
15/01/2005 17:49:02
General information
Forum:
Visual FoxPro
Category:
Reports & Report designer
Environment versions
Visual FoxPro:
VFP 7 SP1
OS:
Windows 2000 SP4
Database:
Visual FoxPro
Miscellaneous
Thread ID:
00976932
Message ID:
00977534
Views:
27
Those left fielders are just what's needed, Al. As you said, all the common causes have been covered. I got to the point where I'd tried everything I could think of and just felt like I was spinning my wheels in the mud. These questions you've asked and George's response earlier have helped me think of a new approach to narrow down problem. I'm going to test the reports with UDFs vs. those without, reports where the view already exists vs. those where I use a views from the DE, reports where I hack the frx before running vs. those whose frx is never modified. Hopefully a pattern will emerge.

In answer to your questions (as best I can):

-I don't think the UDFs are especially complex or that the reports take long to run. I try to be good with clean-up, but I'll double-check the work areas.

-Data source? Again, every flavor. What I originally referred to as "simple listings" are generally a dump of a cursor belonging to a data entry form, so the cursor exists before I call the report. Some are views in the DE and some are cursors created in the report's Init.

-In the debugging I've been doing for the last couple of weeks, I have not been calling the reports from any form that has a grid. There are some such situations in the app, but in all cases the user would leave the grid to click a Print List button to call the report.

-No ActiveX in the app. The problem exists here and at client sites. Each site is a separate company in a different state, so no "corporate standard" in hardware or other software that may be running on the machines. As I said originally, I'd even be surprised if any two machines at a single site are identical.

For this reason, I'm thinking it must be something I'm doing wrong - someplace I'm not cleaning up after myself, for instance- but I ran out of things to look for. Now I have another way to divide and conquer the problem.

I'll take a look at these things you suggested, Al. If you happen to be out there in left field again and come across anything else, I'd love to hear about it!

Thanks again!
Laura
Previous
Reply
Map
View

Click here to load this message in the networking platform