Fields overflow their boundaries when viewed with Active-X viewer

[bikejockey]

Crystal Reports V9
Crystal Enterprise V9
Using Active-X viewer

Reports format fine in when in CR, but when viewing in the
Active-X viewer, fields overflow their boundaries. They don't clip at the field size, they just overprint the following fields (or previous fields if the field is right justified). I know this problem existed earlier but was supposedly fixed. I've tried the latest monthly hotfixes and even the latest weekly hotfixes, but still have the error.

I have search the disk for possible old dll's, none. I have searched the registry checking verions of the viewer and it is the latest version.

I have tried designing the report against different printers, checked printer drivers on the machine the report was created against and the one that CE is running on. I've installed printers to make sure that the printer it was designed against is available on the CE machine. I've installed Acrobat Distiller on both machines and set that as the printer, but same results.

I do have my services running under the "system account". I can't log into that account and set a default printer for it. However, the system default printer for both machines is the same.

I've read the articles on Crystal's website about possible issues. It's not that it render's the font differently and the field or report is clipped. It's that the report is ignoring the field size.

Also, I can click on a field in the viewer and the red box it draws around the field is the correct size, but the text for the field just keep right on going.

 

[ciscowiz]

Hey I am having the same issue and I was wondering if you ever got this resolved.

 

[bikejockey]

No, I never could get the problem fixed. The java viewer has the same problem. In some reports I wound up setting the can grow flag on the field to yes and setting the max rows on the field to 1 as a work around. This truncates the field at a word break. It's not always a great workaround, but it has helped in some reports that were otherwise unreadable where you had the overprinting.

 

[kcgamz]

The work-around suggested by bikejockey is the only solution I've found. See the thread at

http://www.tek-tips.com/viewthread.cfm?SQID=827443&SPID=782&newpid=782&page=1

for a more detailed explanation.

Jerry