Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Preview does not match print, why?

Status
Not open for further replies.

Terris

IS-IT--Management
Jul 26, 2002
27
US
I have modified an existing report by adding an addtional table. The join does work and the tables are relating because the preview shows the data I require. The clincher the printout does not all the time. I have tested all sorts of conditions, thinking first of corrupted data. Once the report gets to a certain page count the preview is right the printout is missing the new joined table information. I have narrowed it down to somewhere between 17 to 25 pages but need to keep killing trees to determine exactly where it dies. any ideas
 
Terris

Is it possible the data in dataenvironment is being use instead of the actual data? Mike Gagnon

If you want to get the best response to a question, please check out FAQ184-2483 first.
 
Are you running the report from data that has been queried as a snapshot or running it directly against live data that could be changing as you print it due to ongoing user input?
I can't tell from your description of "join" whether you're referring to a SQL SELECT involving JOINs or you are referring to joins developed via SET RELATION statements.
 
Ok I'll try to explain as much as possible. I am limited on some information as I am only allowed to customize reports within an existing software package. What I can tell you is the program creates a cursor which is defined in the database. This cursor is joined with quite a few tables (10-12). I, in turn, joined on of the tables associated with the cursor with another table. The tables in question jopest (job in process est) stores the fjobno and the lstoper, I joined this table with jodrtg (job order routing) using a predefined index in jodrtg called fjobnooper (defined as fjobno + str(joperno,4). I am joining to the jopest table using fjobno + str(lstoper,4). Orginally I was looking to pull just qtys but because of the difference between preview and print I added both keys to the report. Wanted to print them out to see what was dropping. When I preview both keys show and qty values display. When I print (more then 18 or so pages) the jodrtg key disappears and both qtys are 0. the jodrtg table is the one added with the new join. Keep in mind if I print less then a certain number of pages (by applying a range of part numbers to select) the information displays on the preview and the printout. I am by no means an experienced foxpro developer but have spent years developing in different types of software and this one has me scratching my head.
 
I must say that I know of nothing that would make the preview different than the actual report...besides a few tricks/hacks that you obviously are not using given that you are just modifying an existing working report. What you see in the preview is what you should see during print if they are both running off the same data set...if you can preview and page through the report all the way and everything looks fine and then when you click the print button from the preview toolbar you get something different and wrong on the print out then I too am scratching my head...sorry I haven't an answer for you. Will be curious to see what is causing it so whenever you or one of the members get it figured out I will look back at this post. Slighthaze = NULL
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top