This subreport resides in a section with other data that will always print.

What is happening, which never did with our VB6 app, is that the report is putting a fine border around the entire subreport even though the subreport is blank and is defined with all Borders set to None.  It's as though it is showing the space where a subreport would print data.

 

I need to have the subreport suppressed totally, without any borders.  Why is it showing?

 

I have even tried moving the subreport to the section above where it noramally prints and suppressing it there..same results. 

 

We are using VB.NET 2005 and Crystal XI Release 2 (w/Service Pack 2).

We are using Crystal Reports for .NET's object models.

 

We develop our reports and CRXIR2, but use our vb.net program to run the report.

 

Any help will be appreciated.  Thank you.

 

We have one field in the report.  It is a 'picture' type field.  It displays an image if the image exists in the database, otherwise blank. 

 

So, Crystal is displaying a blank image with a border around it.  How do I prevent this from displaying at all?  The field itself has all the border line styles set to None the Border color is set to black, but no borders should be printing at all, so the border color should not apply.

 

I don't understand why this is happening.

 

I just tried putting a white border around the image (with all the border lines styles still set to None) and a thin black border prints around the blank image.

 

The subreport runs an SQL stored procedure.  We insert the results into a temp table.  One of the columns in the table is a bit field that will tell us whether or not rows were returned.

 

Well, rows were always getting returned even if the picture/blob/image field was blank.  Why?  The image is defined as a nullable image in the database, so it was always returning something because of the null value in the image.  So the rows returned was always true.  I needed to add an image is not null statement to the where clause in the stored procedure (or modify each subreport and add IsNull(image) to each image's suppress condition).  It was easier to modify one sql stored procedure.

 

Problem solved.  Although we never had this problem with our VB6 application...just with the .NET applications.