Page 1 of 1
					
				R&R Failure on Large Files
				Posted: Tue Feb 01, 2005 5:19 pm
				by Eugene_Feather_(Guest)
				I^m running into a problem with R&R 10 - SQL Version.____I have a SQL Server table in which 1.2 million records are selected.  R&R isolates them, goes through the whole sort and merge process and then dies right before generating output.  If I try a Print Preview, I get the error "rsw.exe App Ver 10.0.11.0, ModName rrsql08.dll, Mod Ver 2.10.0.0, Offset: 0003efda.  Then, it gives me "The instruction at 0x73dd1351 referenced memory at 0x000000000004.  The memory could not be "read"____If I skip print preview and go directly to print, it goes through the sort/merge process and then just quits - no error messages; it just stops.____I^m not actually trying to print anything from the detail records.  I^ve tried this with Record Lines suppressed and with no record line at all.  It doesn^t seem to make any difference.____Thanks........Gene
			 
			
					
				=> RE: R&R Failure on Large Files
				Posted: Wed Feb 02, 2005 2:52 pm
				by kfleming
				It sounds like R&R must be doing a local sort rather than sending the sort as an order by.  Are you sorting on a calculated field or a total?____It could be the number of sort files that is killing things.____Kathleen__R&R Support
			 
			
					
				==> RE: R&R Failure on Large Files
				Posted: Wed Feb 02, 2005 5:09 pm
				by Eugene_Feather_(Guest)
				The report in question was, in fact, sorting on a calculated field.  It was the third of three fields.  Removing it didn^t solve the problem.  With it removed, R&R didn^t use an external sort, but it still failed in the same way.____I tried running this with an older version of R&R, and it failed in exactly the same way.____As an aside here, is there a known problem with sorting on calculated fields as well?____Gene.....
			 
			
					
				===> RE: R&R Failure on Large Files
				Posted: Wed Feb 02, 2005 7:52 pm
				by Peggy_Kuhn_(Guest)
				We^ve seen a similar problem after about 200 pages that have some minor graphics on them.  Our workaround was to print page 1-200, then 201-400, etc.