Welcome To The Home Of The Visual FoxPro Experts  
home. signup. forum. archives. search. google. articles. downloads. faq. members. weblogs. file info. rss.
 From: Ken Murphy
  Where is Ken Murphy?
 Springhill
 Canada
 Ken Murphy
 To: JLW Smith
  Where is JLW Smith?
 
 United Kingdom
 JLW Smith
 Tags
Subject: RE: Urgent Report Problem!
Thread ID: 78567 Message ID: 78648 # Views: 1 # Ratings: 0
Version: Visual FoxPro 8 Category: Reports and Printers
Date: Thursday, October 06, 2005 2:10:21 PM         
   


Most strange indeed.

You mention that you first prepare a table that you use as the basis for your report form. I always do this. I typically use a select statement to create a flat file cursor that only contains exactly the info that I wish to report. I see this as an extension of the "n tier" programming concept. Output data is a tier, and the output itself is a tier. This means that I create the output data and can then use any output device that I want to report the data (reports, labels, HTML, XML, etc.) I never use filters on the report call (REPORT FORM ... FOR ...) nor do I apply a filter to the data environment tables in the report. By doing this, I can create the report cursor using any number of selection criteria and then re-use the same report form.

As this seems to have solved your problem, I recommend you continue to do this.

Ken

> These were my first ports of call. It is a strange one...
>
>
> The report had a filter set on cursor1, a date range and an account number. Instead of this, I create now a temp table with data extracted from the DBF, and set the report to the new temporary DBF, so problem put off, not solved.
>
> The DBF which the filter was set on has no errors, I have re-packed and indexed the table, and could find no problems.
>
> As I have resolved this, it is no longer as pressing, it is now a matter of interest!!!
>
> Thanks for the reply. Any further ideas?
>
> > > I am writing in FP8 SP1, and have encountered a problem with some sites.
> > >
> > > Basically, a report appears whic h has only 1 table, which is filtered in the cursor properties. The report has a problem whereby a FATAL EXCEPTION occurs, but ONLY IF:
> > >
> > > the user exits the report, having pressed the SKIP TO LAST PAGE button.
> > > IF the users scrolls to the last page using the step button, then EXITS, its OK!
> > >
> > > Has anybody heard of this? I have re-built the exe's but to no avail!
> > >
> > > Thanks to anyone who can help.

> >
> > This seems like very odd behaviour. I would check the following:
> > 1. Do you have the latest printer drivers?
> > 2. Is there an index involved and is that index corrupt?
> > 3. Is the table corrupt?
> >
> > Ken

>
>
>
> Thanks!


ENTIRE THREAD

Urgent Report Problem! Posted by JLW Wade @ 10/5/2005 4:49:55 PM
RE: Urgent Report Problem! Posted by Ken Murphy @ 10/5/2005 5:50:22 PM
RE: Urgent Report Problem! Posted by JLW Wade @ 10/6/2005 12:03:18 AM
RE: Urgent Report Problem! Posted by Ken Murphy @ 10/6/2005 2:10:21 PM